Changeset 958


Ignore:
Timestamp:
Jul 27, 2010, 8:46:23 PM (9 years ago)
Author:
fielding@…
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r957 r958  
    12071207      </p>
    12081208      <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>
    1209       <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
    1210          message-body differs from the payload body only when a transfer-coding has been applied, as indicated by the Transfer-Encoding
    1211          header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;9.7</a>).
    1212       </p>
     1209      <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>
    12131210      <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
    1214 </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,
    1215          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,
    1216          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>.
     1211</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
     1212         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
     1213         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>.
    12171214      </p>
    12181215      <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

    r957 r958  
    12501250<t>
    12511251   The message-body (if any) of an HTTP message is used to carry the
    1252    payload body associated with the request or response. The message-body
    1253    differs from the payload body only when a transfer-coding has been
    1254    applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
     1252   payload body associated with the request or response.
    12551253</t>
    12561254<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
     
    12581256</artwork></figure>
    12591257<t>
    1260    When one or more transfer-codings are applied to a payload body,
    1261    usually for the sake of stream-delimiting or data compression, the
    1262    Transfer-Encoding header field &MUST; be provided with the list of
     1258   The message-body differs from the payload body only when a transfer-coding
     1259   has been applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).  When one or more transfer-codings are
     1260   applied to a payload in order to form the message-body, the
     1261   Transfer-Encoding header field &MUST; contain the list of
    12631262   transfer-codings applied. Transfer-Encoding is a property of the message,
    12641263   not of the payload, and thus &MAY; be added or removed by any implementation
Note: See TracChangeset for help on using the changeset viewer.