Ignore:
Timestamp:
04/12/12 12:58:55 (8 years ago)
Author:
fielding@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2027 r2030  
    32223222  <iref primary="true" item="408 Request Timeout (status code)" x:for-anchor=""/>
    32233223<t>
    3224    The client did not produce a request within the time that the server
    3225    was prepared to wait. The client &MAY; repeat the request without
    3226    modifications at any later time.
     3224   The server did not receive a complete request message within the time that
     3225   it was prepared to wait. If the client has sent a request, it &MAY; repeat
     3226   that request, possibly on a new connection if the server indicates that the
     3227   present connection is being closed.
    32273228</t>
    32283229</section>
     
    41244125<t>
    41254126   A definition for a new status code ought to explain the request
    4126    conditions that produce a response containing that status code (e.g.,
     4127   conditions that would cause a response containing that status code (e.g.,
    41274128   combinations of request header fields and/or method(s)) along with any
    41284129   dependencies on response header fields (e.g., what fields are required
     
    47554756   Since tunneled data is opaque to the proxy, there are additional
    47564757   risks to tunneling to other well-known or reserved ports.
    4757    A HTTP client CONNECTing to port 25 could relay spam
     4758   An HTTP client CONNECTing to port 25 could relay spam
    47584759   via SMTP, for example. As such, proxies &SHOULD; restrict CONNECT
    47594760   access to a small number of known ports.
     
    58065807</t>
    58075808<t>
    5808   The requirement to produce a <x:ref>Via</x:ref> header field has been moved
     5809  The requirement to generate a <x:ref>Via</x:ref> header field has been moved
    58095810  from the description of the <x:ref>Server</x:ref> header field to
    58105811  &header-via;.
Note: See TracChangeset for help on using the changeset viewer.