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/p1-messaging.xml

    r2477 r2480  
    17111711   Any Content-Length field value greater than or equal to zero is valid.
    17121712   Since there is no predefined limit to the length of a payload, a
    1713    recipient &SHOULD; anticipate potentially large decimal numerals and
     1713   recipient &MUST; anticipate potentially large decimal numerals and
    17141714   prevent parsing errors due to integer conversion overflows
    17151715   (<xref target="attack.protocol.element.size.overflows"/>).
     
    54145414    </t>
    54155415    <t>
     5416      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
     5417      "integer value parsing"
     5418    </t>
     5419    <t>
    54165420      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/517"/>:
    54175421      "move IANA registrations to correct draft"
Note: See TracChangeset for help on using the changeset viewer.