Changeset 2298 for draft-ietf-httpbis/latest

Timestamp:

20/06/13 17:09:06 (7 years ago)

Author:

julian.reschke@…

Message:

clarify proxy handling of bad content lengths (see #482)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (2 diffs)
• p1-messaging.xml (modified) (2 diffs)

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

@@ -1476 +1476 @@
          <li>
             <p>If a message is received without <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> and with either multiple <a href="#header.content-length" class="smpl">Content-Length</a> header fields having differing field-values or a single Content-Length header field having 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 <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a> status code and then close the connection. If this is a response message received by a proxy, the proxy <em class="bcp14">MUST</em> discard the received response, send a <a href="p2-semantics.html#status.502" class="smpl">502 (Bad Gateway)</a> status code as its downstream response, and then close the connection. If this is a response message received by a user agent,
-               it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection.
+               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 <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a> status code and then close the connection. If this is a response message received by a proxy, the proxy <em class="bcp14">MUST</em> close the connection to the server, discard the received response, and send a <a href="p2-semantics.html#status.502" class="smpl">502 (Bad Gateway)</a> response to the client. If this is a response message received by a user agent, it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection.
             </p>
          </li>
@@ -3219 +3218 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/477">http://tools.ietf.org/wg/httpbis/trac/ticket/477</a>&gt;: "Pipelining language"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/482">http://tools.ietf.org/wg/httpbis/trac/ticket/482</a>&gt;: "proxy handling of a really bad Content-Length"
          </li>
       </ul>

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

@@ -1744 +1744 @@
      a <x:ref>400 (Bad Request)</x:ref> status code and then close the connection.
      If this is a response message received by a proxy, the proxy
-     &MUST; discard the received response, send a <x:ref>502 (Bad Gateway)</x:ref>
-     status code as its downstream response, and then close the connection.
+     &MUST; close the connection to the server, discard the received response,
+     and send a <x:ref>502 (Bad Gateway)</x:ref> response to the client.
      If this is a response message received by a user agent, it &MUST; be
      treated as an error by discarding the message and closing the connection.
@@ -5418 +5418 @@
       "Pipelining language"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/482"/>:
+      "proxy handling of a really bad Content-Length"
+    </t>
   </list>
 </t>