Changeset 1727 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 05/07/12 17:06:19 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1726 r1727 1287 1287 HTTP does not place a pre-defined limit on the length of header fields, 1288 1288 either in isolation or as a set. A server &MUST; be prepared to receive 1289 request header fields of unbounded length and respond with a 4xx status1290 code if the received header field(s) would be longer than the server wishes1291 to handle.1289 request header fields of unbounded length and respond with a <x:ref>4xx 1290 (Client Error)</x:ref> status code if the received header field(s) would be 1291 longer than the server wishes to handle. 1292 1292 </t> 1293 1293 <t> … … 1482 1482 Content-Length, etc.) only indicate what their values would have been 1483 1483 if the request method had been GET. 1484 Successful (2xx)responses to CONNECT switch to tunnel mode instead of1484 <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel mode instead of 1485 1485 having a message body. 1486 All 1xx (Informational), <x:ref>204 (No Content)</x:ref>, and <x:ref>3041486 All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and <x:ref>304 1487 1487 (Not Modified)</x:ref> responses &MUST-NOT; include a message body. 1488 1488 All other responses do include a message body, although the body … … 1649 1649 </t></x:lt> 1650 1650 <x:lt><t> 1651 Any successful (2xx)response to a CONNECT request implies that the1651 Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request implies that the 1652 1652 connection will become a tunnel immediately after the empty line that 1653 1653 concludes the header fields. A client &MUST; ignore any Content-Length … … 2669 2669 order sent on that connection and &MUST; associate each received response 2670 2670 message to the highest ordered request that has not yet received a final 2671 (non- 1xx) response.2671 (non-<x:ref>1xx</x:ref>) response. 2672 2672 </t> 2673 2673 </section> … … 2761 2761 An HTTP/1.1 server that does not support persistent connections &MUST; 2762 2762 include the "close" connection option in every response message that 2763 does not have a 1xx (Informational)status code.2763 does not have a <x:ref>1xx (Informational)</x:ref> status code. 2764 2764 </t> 2765 2765 </section> … … 3194 3194 client and did not include an Expect header field with 3195 3195 the "100-continue" expectation. This requirement overrides the 3196 general rule for forwarding of 1xxresponses (see &status-1xx;).3196 general rule for forwarding of <x:ref>1xx</x:ref> responses (see &status-1xx;). 3197 3197 </t> 3198 3198 </list> … … 3272 3272 The Upgrade header field cannot be used to indicate a switch to a 3273 3273 protocol on a different connection. For that purpose, it is more 3274 appropriate to use a 3xx redirectionresponse (&status-3xx;).3274 appropriate to use a <x:ref>3xx (Redirection)</x:ref> response (&status-3xx;). 3275 3275 </t> 3276 3276 <t> … … 4109 4109 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/> 4110 4110 <x:source href="p2-semantics.xml" basename="p2-semantics"> 4111 <x:defines>1xx (Informational)</x:defines> 4112 <x:defines>1xx</x:defines> 4111 4113 <x:defines>100 (Continue)</x:defines> 4112 4114 <x:defines>101 (Switching Protocols)</x:defines> 4115 <x:defines>2xx (Successful)</x:defines> 4116 <x:defines>2xx</x:defines> 4113 4117 <x:defines>200 (OK)</x:defines> 4114 4118 <x:defines>204 (No Content)</x:defines> 4119 <x:defines>3xx (Redirection)</x:defines> 4120 <x:defines>3xx</x:defines> 4115 4121 <x:defines>301 (Moved Permanently)</x:defines> 4122 <x:defines>4xx (Client Error)</x:defines> 4123 <x:defines>4xx</x:defines> 4116 4124 <x:defines>400 (Bad Request)</x:defines> 4117 4125 <x:defines>405 (Method Not Allowed)</x:defines>
Note: See TracChangeset
for help on using the changeset viewer.