Changeset 1031

Timestamp:

14/10/10 08:22:59 (12 years ago)

Author:

julian.reschke@…

Message:

multiple content-length headers in response -> SHOULD discard (see #95)

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -404 +404 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-10-11">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-10-14">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
@@ -435 +435 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 14, 2011</td>
+               <td class="left">Expires: April 17, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -488 +488 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 11, 2010</td>
+               <td class="right">October 14, 2010</td>
             </tr>
          </tbody>
@@ -516 +516 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 14, 2011.</p>
+      <p>This Internet-Draft will expire on April 17, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1258 +1258 @@
                header field with an invalid value, then the message framing is invalid and <em class="bcp14">MUST</em> be treated as an error to prevent request or response smuggling. If this is a request message, the server <em class="bcp14">MUST</em> respond with a 400 (Bad Request) status code and then close the connection. If this is a response message received by a proxy
                or gateway, the proxy or gateway <em class="bcp14">MUST</em> discard the received response, send a 502 (Bad Gateway) status code as its downstream response, and then close the connection.
-               If this is a response message received by a user-agent, the message-body length is determined by reading the connection until
-               it is closed; an error <em class="bcp14">SHOULD</em> be indicated to the user.
+               If this is a response message received by a user-agent, it <em class="bcp14">SHOULD</em> be treated as an error by discarding the message and closing the connection.
             </p>
          </li>

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

@@ -1347 +1347 @@
      or gateway &MUST; discard the received response, send a 502 (Bad Gateway)
      status code as its downstream response, and then close the connection.
-     If this is a response message received by a user-agent, the message-body
-     length is determined by reading the connection until it is closed;
-     an error &SHOULD; be indicated to the user.
+     If this is a response message received by a user-agent, it &SHOULD; be
+     treated as an error by discarding the message and closing the connection.
     </t></x:lt>
     <x:lt><t>