Changes between Initial Version and Version 2 of Ticket #507


Ignore:
Timestamp:
Nov 4, 2013, 2:49:20 PM (6 years ago)
Author:
julian.reschke@…
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #507

    • Property Severity changed from In WG Last Call to In IETF LC
  • Ticket #507 – Description

    initial v2  
    11P1, Content-Length:
    22
    3 Any Content-Length field value greater than or equal to zero is valid. Since there is no predefined limit to the length of a payload, a recipient SHOULD anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (Section 9.3).
     3  Any Content-Length field value greater than or equal to zero is valid. Since there is no predefined limit to the length of a payload, a recipient SHOULD anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (Section 9.3).
    44
    55P5, Byte-Ranges:
    66
    7 In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-length are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
     7  In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-length are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
    88
    99