Changeset 276 for draft-ietf-httpbis/latest

Timestamp:

Jul 9, 2008, 4:21:44 AM (12 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (4 diffs)
• p1-messaging.xml (modified) (3 diffs)

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

@@ -477 +477 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">July 7, 2008</td>
+            <td class="header right">July 9, 2008</td>
          </tr>
       </table>
@@ -1232 +1232 @@
 </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>).
       </p>
-      <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,
-         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
+      <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
+         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
          (<a href="#message.length" title="Message Length">Section&nbsp;4.4</a>).
       </p>
@@ -1397 +1397 @@
          </li>
          <li>
-            <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.
+            <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
+               and the "chunked" transfer-coding is not present, the transfer-length is defined by the sender closing the connection.
             </p>
          </li>
@@ -2716 +2717 @@
       <p id="rfc.section.E.5.p.1">Closed issues: </p>
       <ul>
+         <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"
+         </li>
          <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"
          </li>

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

@@ -1314 +1314 @@
 <t>
    Whenever a transfer-coding is applied to a message-body, the set of
-   transfer-codings &MUST; include "chunked", unless the message is
-   terminated by closing the connection. When the "chunked" transfer-coding
+   transfer-codings &MUST; include "chunked", unless the message indicates it
+   is terminated by closing the connection. When the "chunked" transfer-coding
    is used, it &MUST; be the last transfer-coding applied to the
    message-body. The "chunked" transfer-coding &MUST-NOT; be applied more
@@ -1649 +1649 @@
     <x:lt><t>
      If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>)
-     is present, then the transfer-length is
-     defined by use of the "chunked" transfer-coding (<xref target="transfer.codings"/>),
-     unless the message is terminated by closing the connection.
+     is present and the "chunked" transfer-coding (<xref target="transfer.codings"/>)
+     is used, the transfer-length is defined by the use of this transfer-coding.
+     If a Transfer-Encoding header field is present and the "chunked" transfer-coding
+     is not present, the transfer-length is defined by the sender closing the connection. 
     </t></x:lt>
     <x:lt><t>
@@ -4554 +4555 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/28"/>:
+      "Connection closing"
+    </t>
+    <t>
       <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/120"/>:
       "need new URL for PAD1995 reference"