Changeset 2030 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

04/12/12 12:58:55 (10 years ago)

Author:

fielding@…

Message:

(editorial) Deal with first half of mnot p1 feedback; addresses #408

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (4 diffs)

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

@@ -3222 +3222 @@
   <iref primary="true" item="408 Request Timeout (status code)" x:for-anchor=""/>
 <t>
-   The client did not produce a request within the time that the server
-   was prepared to wait. The client &MAY; repeat the request without
-   modifications at any later time.
+   The server did not receive a complete request message within the time that
+   it was prepared to wait. If the client has sent a request, it &MAY; repeat
+   that request, possibly on a new connection if the server indicates that the
+   present connection is being closed.
 </t>
 </section>
@@ -4124 +4125 @@
 <t>
    A definition for a new status code ought to explain the request
-   conditions that produce a response containing that status code (e.g.,
+   conditions that would cause a response containing that status code (e.g.,
    combinations of request header fields and/or method(s)) along with any 
    dependencies on response header fields (e.g., what fields are required
@@ -4755 +4756 @@
    Since tunneled data is opaque to the proxy, there are additional 
    risks to tunneling to other well-known or reserved ports. 
-   A HTTP client CONNECTing to port 25 could relay spam
+   An HTTP client CONNECTing to port 25 could relay spam
    via SMTP, for example. As such, proxies &SHOULD; restrict CONNECT 
    access to a small number of known ports.
@@ -5806 +5807 @@
 </t>
 <t>
-  The requirement to produce a <x:ref>Via</x:ref> header field has been moved
+  The requirement to generate a <x:ref>Via</x:ref> header field has been moved
   from the description of the <x:ref>Server</x:ref> header field to
   &header-via;.