Changeset 2060

Timestamp:

29/12/12 02:06:37 (9 years ago)

Author:

fielding@…

Message:

(editorial) slight rephrasing of 408

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires June 30, 2013"; 
+       content: "Expires July 1, 2013"; 
   } 
   @bottom-right {
@@ -495 +495 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-12-27">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-12-28">
       <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. 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>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">December 27, 2012</td>
+               <td class="right">December 28, 2012</td>
             </tr>
             <tr>
-               <td class="left">Expires: June 30, 2013</td>
+               <td class="left">Expires: July 1, 2013</td>
                <td class="right"></td>
             </tr>
@@ -554 +554 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on June 30, 2013.</p>
+      <p>This Internet-Draft will expire on July 1, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <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>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
       <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.
-         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.
+         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
+         the client has an outstanding request in transit, the client <em class="bcp14">MAY</em> repeat that request on a new connection.
       </p>
       <div id="rfc.iref.74"></div>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -3204 +3204 @@
    The <x:dfn>408 (Request Timeout)</x:dfn> status code indicates
    that the server did not receive a complete request message within the time
-   that it was prepared to wait. Since the only reason to send this message
-   is if the server has decided to close the connection, the server &SHOULD;
-   indicate that intent with the <x:ref>close</x:ref> connection option
-   (&header-connection;). If the client has an outstanding request in transit,
+   that it was prepared to wait.
+   A server &SHOULD; send the <x:ref>close</x:ref> connection option
+   (&header-connection;) in the response, since 408 implies that the server
+   has decided to close the connection rather than continue waiting.
+   If the client has an outstanding request in transit,
    the client &MAY; repeat that request on a new connection.
 </t>