Changeset 2147 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

21/01/13 07:43:33 (9 years ago)

Author:

fielding@…

Message:

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

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1535 +1535 @@
 <t>
    Unlike <x:ref>Content-Encoding</x:ref> (&content-codings;),
-   Transfer-Encoding is a property of the message, not of the payload, and
+   Transfer-Encoding is a property of the message, not of the representation, and
    any recipient along the request/response chain &MAY; decode the received
    transfer coding(s) or apply additional transfer coding(s) to the message
@@ -1636 +1636 @@
 <t>
    Any Content-Length field value greater than or equal to zero is valid.
-   Since there is no predefined limit to the length of an HTTP payload,
+   Since there is no predefined limit to the length of a payload,
    recipients &SHOULD; anticipate potentially large decimal numerals and
    prevent parsing errors due to integer conversion overflows