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

Timestamp:

Jul 27, 2010, 8:46:23 PM (9 years ago)

Author:

fielding@…

Message:

(editorial) move sentence down to keep paragraph topics simple.

File:

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

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

@@ -1250 +1250 @@
 <t>
    The message-body (if any) of an HTTP message is used to carry the
-   payload body associated with the request or response. The message-body
-   differs from the payload body only when a transfer-coding has been
-   applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
+   payload body associated with the request or response.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
@@ -1258 +1256 @@
 </artwork></figure>
 <t>
-   When one or more transfer-codings are applied to a payload body,
-   usually for the sake of stream-delimiting or data compression, the
-   Transfer-Encoding header field &MUST; be provided with the list of
+   The message-body differs from the payload body only when a transfer-coding
+   has been applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).  When one or more transfer-codings are
+   applied to a payload in order to form the message-body, the
+   Transfer-Encoding header field &MUST; contain the list of
    transfer-codings applied. Transfer-Encoding is a property of the message,
    not of the payload, and thus &MAY; be added or removed by any implementation