Changeset 276


Ignore:
Timestamp:
Jul 9, 2008, 4:21:44 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #28: clarify connection closing vs chunked encoding (closes #28).

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

Legend:

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

    r275 r276  
    477477         <tr>
    478478            <td class="header left"></td>
    479             <td class="header right">July 7, 2008</td>
     479            <td class="header right">July 9, 2008</td>
    480480         </tr>
    481481      </table>
     
    12321232</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>).
    12331233      </p>
    1234       <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,
    1235          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
     1234      <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
     1235         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
    12361236         (<a href="#message.length" title="Message Length">Section&nbsp;4.4</a>).
    12371237      </p>
     
    13971397         </li>
    13981398         <li>
    1399             <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.
     1399            <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
     1400               and the "chunked" transfer-coding is not present, the transfer-length is defined by the sender closing the connection.
    14001401            </p>
    14011402         </li>
     
    27162717      <p id="rfc.section.E.5.p.1">Closed issues: </p>
    27172718      <ul>
     2719         <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"
     2720         </li>
    27182721         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120</a>&gt;: "need new URL for PAD1995 reference"
    27192722         </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r275 r276  
    13141314<t>
    13151315   Whenever a transfer-coding is applied to a message-body, the set of
    1316    transfer-codings &MUST; include "chunked", unless the message is
    1317    terminated by closing the connection. When the "chunked" transfer-coding
     1316   transfer-codings &MUST; include "chunked", unless the message indicates it
     1317   is terminated by closing the connection. When the "chunked" transfer-coding
    13181318   is used, it &MUST; be the last transfer-coding applied to the
    13191319   message-body. The "chunked" transfer-coding &MUST-NOT; be applied more
     
    16491649    <x:lt><t>
    16501650     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>)
    1651      is present, then the transfer-length is
    1652      defined by use of the "chunked" transfer-coding (<xref target="transfer.codings"/>),
    1653      unless the message is terminated by closing the connection.
     1651     is present and the "chunked" transfer-coding (<xref target="transfer.codings"/>)
     1652     is used, the transfer-length is defined by the use of this transfer-coding.
     1653     If a Transfer-Encoding header field is present and the "chunked" transfer-coding
     1654     is not present, the transfer-length is defined by the sender closing the connection.
    16541655    </t></x:lt>
    16551656    <x:lt><t>
     
    45544555  <list style="symbols">
    45554556    <t>
     4557      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28"/>:
     4558      "Connection closing"
     4559    </t>
     4560    <t>
    45564561      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120"/>:
    45574562      "need new URL for PAD1995 reference"
Note: See TracChangeset for help on using the changeset viewer.