* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #28: i28.2.diff

File i28.2.diff, 6.6 KB (added by julian.reschke@gmx.de, 7 years ago)

Proposed patch.

  • p1-messaging.xml

     
    12821282</t> 
    12831283<t> 
    12841284   Whenever a transfer-coding is applied to a message-body, the set of 
    1285    transfer-codings &MUST; include "chunked", unless the message is 
    1286    terminated by closing the connection. When the "chunked" transfer-coding 
     1285   transfer-codings &MUST; include "chunked", unless the message indicates it 
     1286   is terminated by closing the connection. When the "chunked" transfer-coding 
    12871287   is used, it &MUST; be the last transfer-coding applied to the 
    12881288   message-body. The "chunked" transfer-coding &MUST-NOT; be applied more 
    12891289   than once to a message-body. These rules allow the recipient to 
     
    16171617    </t></x:lt> 
    16181618    <x:lt><t> 
    16191619     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>) 
    1620      is present, then the transfer-length is 
    1621      defined by use of the "chunked" transfer-coding (<xref target="transfer.codings"/>), 
    1622      unless the message is terminated by closing the connection. 
     1620     is present and the "chunked" transfer-coding (<xref target="transfer.codings"/>) 
     1621     is used, the transfer-length is defined by the use of this transfer-coding. 
     1622     If a Transfer-Encoding header field is present and the "chunked" transfer-coding 
     1623     is not present, the transfer-length is defined by the sender closing the connection.  
    16231624    </t></x:lt> 
    16241625    <x:lt><t> 
    16251626     If a Content-Length header field (<xref target="header.content-length"/>) is present, its 
     
    45234524 
    45244525<section title="Since draft-ietf-httpbis-p1-messaging-03" anchor="changes.since.03"> 
    45254526<t> 
     4527  Closed issues: 
     4528  <list style="symbols">  
     4529    <t> 
     4530      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28"/>: 
     4531      "Connection closing" 
     4532    </t> 
     4533  </list> 
    45264534</t> 
    45274535</section> 
    45284536 
  • p1-messaging.html

     
    476476         </tr> 
    477477         <tr> 
    478478            <td class="header left"></td> 
    479             <td class="header right">July 3, 2008</td> 
     479            <td class="header right">July 5, 2008</td> 
    480480         </tr> 
    481481      </table> 
    482482      <p class="title">HTTP/1.1, part 1: URIs, Connections, and Message Parsing<br><span class="filename">draft-ietf-httpbis-p1-messaging-latest</span></p> 
     
    12001200  <a href="#rule.parameter" class="smpl">value</a>                   = <a href="#rule.token.separators" class="smpl">token</a> | <a href="#rule.quoted-string" class="smpl">quoted-string</a> 
    12011201</pre><p id="rfc.section.3.4.p.5">All transfer-coding values are case-insensitive. HTTP/1.1 uses transfer-coding values in the TE header field (<a href="#header.te" id="rfc.xref.header.te.1" title="TE">Section&nbsp;8.5</a>) and in the Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;8.7</a>). 
    12021202      </p> 
    1203       <p id="rfc.section.3.4.p.6">Whenever a transfer-coding is applied to a message-body, the set of transfer-codings <em class="bcp14">MUST</em> include "chunked", unless the message is terminated by closing the connection. When the "chunked" transfer-coding is used, 
    1204          it <em class="bcp14">MUST</em> be the last transfer-coding applied to the message-body. The "chunked" transfer-coding <em class="bcp14">MUST NOT</em> be applied more than once to a message-body. These rules allow the recipient to determine the transfer-length of the message 
     1203      <p id="rfc.section.3.4.p.6">Whenever a transfer-coding is applied to a message-body, the set of transfer-codings <em class="bcp14">MUST</em> include "chunked", unless the message indicates it is terminated by closing the connection. When the "chunked" transfer-coding 
     1204         is used, it <em class="bcp14">MUST</em> be the last transfer-coding applied to the message-body. The "chunked" transfer-coding <em class="bcp14">MUST NOT</em> be applied more than once to a message-body. These rules allow the recipient to determine the transfer-length of the message 
    12051205         (<a href="#message.length" title="Message Length">Section&nbsp;4.4</a>). 
    12061206      </p> 
    12071207      <p id="rfc.section.3.4.p.7">Transfer-codings are analogous to the Content-Transfer-Encoding values of MIME <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>, which were designed to enable safe transport of binary data over a 7-bit transport service. However, safe transport has 
     
    13651365            </p> 
    13661366         </li> 
    13671367         <li> 
    1368             <p>If a Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;8.7</a>) is present, then the transfer-length is defined by use of the "chunked" transfer-coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>), unless the message is terminated by closing the connection. 
     1368            <p>If a Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;8.7</a>) is present and the "chunked" transfer-coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>) is used, the transfer-length is defined by the use of this transfer-coding. If a Transfer-Encoding header field is present 
     1369               and the "chunked" transfer-coding is not present, the transfer-length is defined by the sender closing the connection. 
    13691370            </p> 
    13701371         </li> 
    13711372         <li> 
     
    26832684         <li>Replace string literals when the string really is case-sensitive (HTTP-Version).</li> 
    26842685      </ul> 
    26852686      <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></h2> 
     2687      <p id="rfc.section.E.5.p.1">Closed issues: </p> 
     2688      <ul> 
     2689         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28</a>&gt;: "Connection closing" 
     2690         </li> 
     2691      </ul> 
    26862692      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 
    26872693      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 
    26882694         authors retain all their rights.