Ignore:
Timestamp:
21/01/13 07:43:33 (8 years ago)
Author:
fielding@…
Message:

(editorial) Fix a few cases where the term payload is used beyond the scope of a message

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2146 r2147  
    15351535<t>
    15361536   Unlike <x:ref>Content-Encoding</x:ref> (&content-codings;),
    1537    Transfer-Encoding is a property of the message, not of the payload, and
     1537   Transfer-Encoding is a property of the message, not of the representation, and
    15381538   any recipient along the request/response chain &MAY; decode the received
    15391539   transfer coding(s) or apply additional transfer coding(s) to the message
     
    16361636<t>
    16371637   Any Content-Length field value greater than or equal to zero is valid.
    1638    Since there is no predefined limit to the length of an HTTP payload,
     1638   Since there is no predefined limit to the length of a payload,
    16391639   recipients &SHOULD; anticipate potentially large decimal numerals and
    16401640   prevent parsing errors due to integer conversion overflows
Note: See TracChangeset for help on using the changeset viewer.