Ignore:
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)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r1764 r1767  
    720720  <x:anchor-alias value="suffix-byte-range-spec"/>
    721721  <x:anchor-alias value="suffix-length"/>
    722 
    723722   A byte range operation &MAY; specify a single range of bytes, or a set
    724723   of ranges within a single representation.
     
    775774   &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code
    776775   containing the satisfiable ranges of the representation.
     776</t>
     777<t>
     778   In the byte range syntax, <x:ref>first-byte-pos</x:ref>,
     779   <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
     780   expressed as decimal number of octets.  Since there is no predefined limit
     781   to the length of an HTTP payload, recipients &SHOULD; anticipate
     782   potentially large decimal numerals and prevent parsing errors due to integer
     783   conversion overflows.
    777784</t>
    778785<t>
     
    17711778      "note introduction of new IANA registries as normative changes"
    17721779    </t>
     1780    <t>
     1781      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/369"/>:
     1782      "range units vs leading zeroes vs size"
     1783    </t>
    17731784  </list>
    17741785</t>
Note: See TracChangeset for help on using the changeset viewer.