Changeset 2030 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 04/12/12 12:58:55 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r2027 r2030 3222 3222 <iref primary="true" item="408 Request Timeout (status code)" x:for-anchor=""/> 3223 3223 <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. 3227 3228 </t> 3228 3229 </section> … … 4124 4125 <t> 4125 4126 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., 4127 4128 combinations of request header fields and/or method(s)) along with any 4128 4129 dependencies on response header fields (e.g., what fields are required … … 4755 4756 Since tunneled data is opaque to the proxy, there are additional 4756 4757 risks to tunneling to other well-known or reserved ports. 4757 A HTTP client CONNECTing to port 25 could relay spam4758 An HTTP client CONNECTing to port 25 could relay spam 4758 4759 via SMTP, for example. As such, proxies &SHOULD; restrict CONNECT 4759 4760 access to a small number of known ports. … … 5806 5807 </t> 5807 5808 <t> 5808 The requirement to produce a <x:ref>Via</x:ref> header field has been moved5809 The requirement to generate a <x:ref>Via</x:ref> header field has been moved 5809 5810 from the description of the <x:ref>Server</x:ref> header field to 5810 5811 &header-via;.
Note: See TracChangeset
for help on using the changeset viewer.