Changeset 1031
- Timestamp:
- 14/10/10 08:22:59 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1028 r1031 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-1 1">406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-14"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <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 "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" 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> 436 436 <tr> 437 <td class="left">Expires: April 1 4, 2011</td>437 <td class="left">Expires: April 17, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">October 1 1, 2010</td>490 <td class="right">October 14, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on April 1 4, 2011.</p>518 <p>This Internet-Draft will expire on April 17, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <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 1259 1259 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. 1262 1261 </p> 1263 1262 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1028 r1031 1347 1347 or gateway &MUST; discard the received response, send a 502 (Bad Gateway) 1348 1348 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. 1352 1351 </t></x:lt> 1353 1352 <x:lt><t>
Note: See TracChangeset
for help on using the changeset viewer.