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

Changeset 1031


Ignore:
Timestamp:
2010-10-14 01:22:59 (4 years ago)
Author:
julian.reschke@gmx.de
Message:

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

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

Legend:

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

    r1028 r1031  
    404404      <meta name="dct.creator" content="Reschke, J. F."> 
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 
    406       <meta name="dct.issued" scheme="ISO8601" content="2010-10-11"> 
     406      <meta name="dct.issued" scheme="ISO8601" content="2010-10-14"> 
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    408408      <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."> 
     
    435435            </tr> 
    436436            <tr> 
    437                <td class="left">Expires: April 14, 2011</td> 
     437               <td class="left">Expires: April 17, 2011</td> 
    438438               <td class="right">HP</td> 
    439439            </tr> 
     
    488488            <tr> 
    489489               <td class="left"></td> 
    490                <td class="right">October 11, 2010</td> 
     490               <td class="right">October 14, 2010</td> 
    491491            </tr> 
    492492         </tbody> 
     
    516516         in progress”. 
    517517      </p> 
    518       <p>This Internet-Draft will expire on April 14, 2011.</p> 
     518      <p>This Internet-Draft will expire on April 17, 2011.</p> 
    519519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    520520      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    12581258               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 
    12591259               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. 
    1260                If this is a response message received by a user-agent, the message-body length is determined by reading the connection until 
    1261                it is closed; an error <em class="bcp14">SHOULD</em> be indicated to the user. 
     1260               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. 
    12621261            </p> 
    12631262         </li> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1028 r1031  
    13471347     or gateway &MUST; discard the received response, send a 502 (Bad Gateway) 
    13481348     status code as its downstream response, and then close the connection. 
    1349      If this is a response message received by a user-agent, the message-body 
    1350      length is determined by reading the connection until it is closed; 
    1351      an error &SHOULD; be indicated to the user. 
     1349     If this is a response message received by a user-agent, it &SHOULD; be 
     1350     treated as an error by discarding the message and closing the connection. 
    13521351    </t></x:lt> 
    13531352    <x:lt><t> 
Note: See TracChangeset for help on using the changeset viewer.