Changeset 564 for draft-ietf-httpbis/latest/p5-range.html

Timestamp:

27/03/09 13:55:35 (13 years ago)

Author:

julian.reschke@…

Message:

move anchor for other-ranges-specifier to correct subsection

File:

• draft-ietf-httpbis/latest/p5-range.html (modified) (4 diffs)

draft-ietf-httpbis/latest/p5-range.html

@@ -467 +467 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">March 24, 2009</td>
+            <td class="header right">March 27, 2009</td>
          </tr>
       </table>
@@ -799 +799 @@
       <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
       <div id="rule.ranges-specifier">
-         <p id="rfc.section.5.4.1.p.3">                  A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.
+         <p id="rfc.section.5.4.1.p.3">                A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.
          </p>
       </div>
@@ -844 +844 @@
       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
   <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
-          / <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a>
-  <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
+          / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
+  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
 </pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
          since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
@@ -1137 +1137 @@
 <a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
 <a href="#range.units" class="smpl">other-range-unit</a> = token
-<a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*CHAR
+<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*CHAR
 
 <a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit