Changeset 1767

Timestamp:

Jul 13, 2012, 8:49:46 AM (7 years ago)

Author:

julian.reschke@…

Message:

Explain that parsers need to be careful with the values in byte ranges (stealing text from definition of Content-Length) (see #369)

Location:

draft-ietf-httpbis/latest

Files:

• p5-range.html (modified) (2 diffs)
• p5-range.xml (modified) (3 diffs)

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

@@ -944 +944 @@
          is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a <a href="#status.416" class="smpl">416 (Requested Range Not Satisfiable)</a> status code. Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a <a href="#status.206" class="smpl">206 (Partial Content)</a> status code containing the satisfiable ranges of the representation.
       </p>
-      <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
+      <p id="rfc.section.5.4.1.p.12">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of an HTTP payload, recipients <em class="bcp14">SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
+      </p>
+      <p id="rfc.section.5.4.1.p.13">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
       <ul>
          <li>The first 500 bytes (byte offsets 0-499, inclusive): 
@@ -1495 +1497 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
          </li>
       </ul>

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

@@ -720 +720 @@
   <x:anchor-alias value="suffix-byte-range-spec"/>
   <x:anchor-alias value="suffix-length"/>
-
    A byte range operation &MAY; specify a single range of bytes, or a set
    of ranges within a single representation.
@@ -775 +774 @@
    &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code
    containing the satisfiable ranges of the representation.
+</t>
+<t>
+   In the byte range syntax, <x:ref>first-byte-pos</x:ref>,
+   <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
+   expressed as decimal number of octets.  Since there is no predefined limit
+   to the length of an HTTP payload, recipients &SHOULD; anticipate
+   potentially large decimal numerals and prevent parsing errors due to integer
+   conversion overflows.
 </t>
 <t>
@@ -1771 +1778 @@
       "note introduction of new IANA registries as normative changes"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/369"/>:
+      "range units vs leading zeroes vs size"
+    </t>
   </list>
 </t>