Changeset 1716 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 04/07/12 20:15:19 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1715 r1716 3091 3091 <section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status"> 3092 3092 <t> 3093 The purpose of the 100 (Continue) status code (see &status-100;) is to3094 allow a client that is sending a request message with a request body3093 The purpose of the <x:ref>100 (Continue)</x:ref> status code (see &status-100;) 3094 is to allow a client that is sending a request message with a request body 3095 3095 to determine if the origin server is willing to accept the request 3096 3096 (based on the request header fields) before the client sends the request … … 3103 3103 <list style="symbols"> 3104 3104 <t> 3105 If a client will wait for a 100 (Continue)response before3105 If a client will wait for a <x:ref>100 (Continue)</x:ref> response before 3106 3106 sending the request body, it &MUST; send an Expect header 3107 3107 field (&header-expect;) with the "100-continue" expectation. … … 3118 3118 ambiguous situations in which a client might send "Expect: 100-continue" 3119 3119 without receiving either a <x:ref>417 (Expectation Failed)</x:ref> 3120 or a 100 (Continue)status code. Therefore, when a client sends this3120 or a <x:ref>100 (Continue)</x:ref> status code. Therefore, when a client sends this 3121 3121 header field to an origin server (possibly via a proxy) from which it 3122 has never seen a 100 (Continue)status code, the client &SHOULD-NOT;3122 has never seen a <x:ref>100 (Continue)</x:ref> status code, the client &SHOULD-NOT; 3123 3123 wait for an indefinite period before sending the request body. 3124 3124 </t> … … 3128 3128 <t> Upon receiving a request which includes an Expect header 3129 3129 field with the "100-continue" expectation, an origin server &MUST; 3130 either respond with 100 (Continue)status code and continue to read3130 either respond with <x:ref>100 (Continue)</x:ref> status code and continue to read 3131 3131 from the input stream, or respond with a final status code. The 3132 3132 origin server &MUST-NOT; wait for the request body before sending 3133 the 100 (Continue)response. If it responds with a final status3133 the <x:ref>100 (Continue)</x:ref> response. If it responds with a final status 3134 3134 code, it &MAY; close the transport connection or it &MAY; continue 3135 3135 to read and discard the rest of the request. It &MUST-NOT; 3136 3136 perform the request method if it returns a final status code. 3137 3137 </t> 3138 <t> An origin server &SHOULD-NOT; send a 100 (Continue)response if3138 <t> An origin server &SHOULD-NOT; send a <x:ref>100 (Continue)</x:ref> response if 3139 3139 the request message does not include an Expect header 3140 3140 field with the "100-continue" expectation, and &MUST-NOT; send a 3141 100 (Continue)response if such a request comes from an HTTP/1.03141 <x:ref>100 (Continue)</x:ref> response if such a request comes from an HTTP/1.0 3142 3142 (or earlier) client. There is an exception to this rule: for 3143 compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)3143 compatibility with <xref target="RFC2068"/>, a server &MAY; send a <x:ref>100 (Continue)</x:ref> 3144 3144 status code in response to an HTTP/1.1 PUT or POST request that does 3145 3145 not include an Expect header field with the "100-continue" 3146 3146 expectation. This exception, the purpose of which is 3147 3147 to minimize any client processing delays associated with an 3148 undeclared wait for 100 (Continue)status code, applies only to3148 undeclared wait for <x:ref>100 (Continue)</x:ref> status code, applies only to 3149 3149 HTTP/1.1 requests, and not to requests with any other HTTP-version 3150 3150 value. 3151 3151 </t> 3152 <t> An origin server &MAY; omit a 100 (Continue)response if it has3152 <t> An origin server &MAY; omit a <x:ref>100 (Continue)</x:ref> response if it has 3153 3153 already received some or all of the request body for the 3154 3154 corresponding request. 3155 3155 </t> 3156 <t> An origin server that sends a 100 (Continue)response &MUST;3156 <t> An origin server that sends a <x:ref>100 (Continue)</x:ref> response &MUST; 3157 3157 ultimately send a final status code, once the request body is 3158 3158 received and processed, unless it terminates the transport … … 3190 3190 numbers received from recently-referenced next-hop servers. 3191 3191 </t> 3192 <t> A proxy &MUST-NOT; forward a 100 (Continue)response if the3192 <t> A proxy &MUST-NOT; forward a <x:ref>100 (Continue)</x:ref> response if the 3193 3193 request message was received from an HTTP/1.0 (or earlier) 3194 3194 client and did not include an Expect header field with … … 3275 3275 </t> 3276 3276 <t> 3277 Servers &MUST; include the "Upgrade" header field in 101 (Switching3278 Protocols) responses to indicate which protocol(s) are being switched to,3277 Servers &MUST; include the "Upgrade" header field in <x:ref>101 (Switching 3278 Protocols)</x:ref> responses to indicate which protocol(s) are being switched to, 3279 3279 and &MUST; include it in <x:ref>426 (Upgrade Required)</x:ref> responses to indicate 3280 3280 acceptable protocols to upgrade to. Servers &MAY; include it in any other … … 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>100 (Continue)</x:defines> 4112 <x:defines>101 (Switching Protocols)</x:defines> 4111 4113 <x:defines>200 (OK)</x:defines> 4112 4114 <x:defines>204 (No Content)</x:defines>
Note: See TracChangeset
for help on using the changeset viewer.