Changeset 2060
- Timestamp:
- 29/12/12 02:06:37 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2059 r2060 449 449 } 450 450 @bottom-center { 451 content: "Expires Ju ne 30, 2013";451 content: "Expires July 1, 2013"; 452 452 } 453 453 @bottom-right { … … 495 495 <meta name="dct.creator" content="Reschke, J. F."> 496 496 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 497 <meta name="dct.issued" scheme="ISO8601" content="2012-12-2 7">497 <meta name="dct.issued" scheme="ISO8601" content="2012-12-28"> 498 498 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 499 499 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 523 523 <tr> 524 524 <td class="left">Intended status: Standards Track</td> 525 <td class="right">December 2 7, 2012</td>525 <td class="right">December 28, 2012</td> 526 526 </tr> 527 527 <tr> 528 <td class="left">Expires: Ju ne 30, 2013</td>528 <td class="left">Expires: July 1, 2013</td> 529 529 <td class="right"></td> 530 530 </tr> … … 554 554 in progress”. 555 555 </p> 556 <p>This Internet-Draft will expire on Ju ne 30, 2013.</p>556 <p>This Internet-Draft will expire on July 1, 2013.</p> 557 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 558 558 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2638 2638 <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a> <a id="status.408" href="#status.408">408 Request Timeout</a></h3> 2639 2639 <p id="rfc.section.6.5.7.p.1">The <dfn>408 (Request Timeout)</dfn> status code indicates that the server did not receive a complete request message within the time that it was prepared to wait. 2640 Since the only reason to send this message is if the server has decided to close the connection, the server <em class="bcp14">SHOULD</em> indicate that intent with the <a href="p1-messaging.html#header.connection" class="smpl">close</a> connection option (<a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). If the client has an outstanding request in transit, the client <em class="bcp14">MAY</em> repeat that request on a new connection. 2640 A server <em class="bcp14">SHOULD</em> send the <a href="p1-messaging.html#header.connection" class="smpl">close</a> connection option (<a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) in the response, since 408 implies that the server has decided to close the connection rather than continue waiting. If 2641 the client has an outstanding request in transit, the client <em class="bcp14">MAY</em> repeat that request on a new connection. 2641 2642 </p> 2642 2643 <div id="rfc.iref.74"></div> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2059 r2060 3204 3204 The <x:dfn>408 (Request Timeout)</x:dfn> status code indicates 3205 3205 that the server did not receive a complete request message within the time 3206 that it was prepared to wait. Since the only reason to send this message 3207 is if the server has decided to close the connection, the server &SHOULD; 3208 indicate that intent with the <x:ref>close</x:ref> connection option 3209 (&header-connection;). If the client has an outstanding request in transit, 3206 that it was prepared to wait. 3207 A server &SHOULD; send the <x:ref>close</x:ref> connection option 3208 (&header-connection;) in the response, since 408 implies that the server 3209 has decided to close the connection rather than continue waiting. 3210 If the client has an outstanding request in transit, 3210 3211 the client &MAY; repeat that request on a new connection. 3211 3212 </t>
Note: See TracChangeset
for help on using the changeset viewer.