Changeset 1514 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 26/01/12 14:54:04 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1511 r1514 896 896 <t> 897 897 Intermediaries that process HTTP messages (i.e., all intermediaries 898 other than those acting as a tunnel) &MUST; send their own HTTP-Version898 other than those acting as tunnels) &MUST; send their own HTTP-Version 899 899 in forwarded messages. In other words, they &MUST-NOT; blindly 900 900 forward the first line of an HTTP message without ensuring that the … … 2794 2794 or until the client closes the connection. Otherwise, the client 2795 2795 might not reliably receive the response message. However, this 2796 requirement isnot be construed as preventing a server from2796 requirement ought not be construed as preventing a server from 2797 2797 defending itself against denial-of-service attacks, or from 2798 2798 badly broken client implementations. … … 3089 3089 <t> 3090 3090 The "TE" header field indicates what extension transfer-codings 3091 it is willing to accept in the response, and whether or not it is3091 the client is willing to accept in the response, and whether or not it is 3092 3092 willing to accept trailer fields in a chunked transfer-coding. 3093 3093 </t> … … 3157 3157 <t> 3158 3158 If the TE field-value is empty or if no TE field is present, the only 3159 transfer-coding is "chunked". A message with no transfer-coding is3159 acceptable transfer-coding is "chunked". A message with no transfer-coding is 3160 3160 always acceptable. 3161 3161 </t> … … 3249 3249 <t> 3250 3250 The Upgrade header field is intended to provide a simple mechanism 3251 for transition from HTTP/1.1 to some other, incompatible protocol. It3251 for transitioning from HTTP/1.1 to some other, incompatible protocol. It 3252 3252 does so by allowing the client to advertise its desire to use another 3253 3253 protocol, such as a later version of HTTP with a higher major version … … 3838 3838 </t> 3839 3839 <t> 3840 Users of a proxy need to be aware that proxies are no trustworthierthan3840 Users of a proxy need to be aware that proxies are no more trustworthy than 3841 3841 the people who run them; HTTP itself cannot solve this problem. 3842 3842 </t> … … 4859 4859 any valid request in the format of HTTP/1.0 and respond appropriately 4860 4860 with an HTTP/1.1 message that only uses features understood (or 4861 safely ignored) by HTTP/1.0 clients. Likewise, w ould expect4861 safely ignored) by HTTP/1.0 clients. Likewise, we would expect 4862 4862 an HTTP/1.1 client to understand any valid HTTP/1.0 response. 4863 4863 </t>
Note: See TracChangeset
for help on using the changeset viewer.