Changeset 958 for draft-ietf-httpbis/latest

Timestamp:

28/07/10 03:46:23 (12 years ago)

Author:

fielding@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (1 diff)
• p1-messaging.xml (modified) (2 diffs)

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

@@ -1207 +1207 @@
       </p>
       <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="message.body" href="#message.body">Message Body</a></h2>
-      <p id="rfc.section.3.3.p.1">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 (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;9.7</a>).
-      </p>
+      <p id="rfc.section.3.3.p.1">The message-body (if any) of an HTTP message is used to carry the payload body associated with the request or response.</p>
       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#message.body" class="smpl">message-body</a> = *OCTET
-</pre><p id="rfc.section.3.3.p.3">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 <em class="bcp14">MUST</em> be provided with the list of transfer-codings applied. Transfer-Encoding is a property of the message, not of the payload,
-         and thus <em class="bcp14">MAY</em> be added or removed by any implementation along the request/response chain under the constraints found in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;6.2</a>.
+</pre><p id="rfc.section.3.3.p.3">The message-body differs from the payload body only when a transfer-coding has been applied, as indicated by the Transfer-Encoding
+         header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;9.7</a>). When one or more transfer-codings are applied to a payload in order to form the message-body, the Transfer-Encoding header
+         field <em class="bcp14">MUST</em> contain the list of transfer-codings applied. Transfer-Encoding is a property of the message, not of the payload, and thus <em class="bcp14">MAY</em> be added or removed by any implementation along the request/response chain under the constraints found in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;6.2</a>.
       </p>
       <p id="rfc.section.3.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p>

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