Ignore:
Timestamp:
07/11/13 15:28:22 (7 years ago)
Author:
julian.reschke@…
Message:

clarify integer parsing requirement (see #507)

File:
1 edited

Legend:

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

    r2477 r2480  
    314314   <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
    315315   expressed as decimal number of octets. Since there is no predefined limit
    316    to the length of a payload, recipients ought to anticipate potentially
     316   to the length of a payload, recipients &MUST; anticipate potentially
    317317   large decimal numerals and prevent parsing errors due to integer conversion
    318318   overflows.
     
    15141514    </t>
    15151515    <t>
     1516      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
     1517      "integer value parsing"
     1518    </t>
     1519    <t>
    15161520      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/508"/>:
    15171521      "broken sentence in description of 206"
Note: See TracChangeset for help on using the changeset viewer.