Changeset 1778
- Timestamp:
- 14/07/12 18:33:05 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1776 r1778 1102 1102 location. 1103 1103 </p> 1104 <p id="rfc.section.2.3.6.p.2">A successful response <em class="bcp14">SHOULD</em> be <a href="#status.200" class="smpl">200 (OK)</a> if the response includes a nrepresentation describing the status, <a href="#status.202" class="smpl">202 (Accepted)</a> if the action has not yet been enacted, or <a href="#status.204" class="smpl">204 (No Content)</a> if the action has been enacted but the response does not include a representation.1104 <p id="rfc.section.2.3.6.p.2">A successful response <em class="bcp14">SHOULD</em> be <a href="#status.200" class="smpl">200 (OK)</a> if the response includes a representation describing the status, <a href="#status.202" class="smpl">202 (Accepted)</a> if the action has not yet been enacted, or <a href="#status.204" class="smpl">204 (No Content)</a> if the action has been enacted but the response does not include a representation. 1105 1105 </p> 1106 1106 <p id="rfc.section.2.3.6.p.3">Bodies on DELETE requests have no defined semantics. Note that sending a body on a DELETE request might cause some existing … … 1664 1664 </p> 1665 1665 <p id="rfc.section.4.3.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself 1666 requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards1666 requested the generation of the 1xx response. (For example, if a proxy adds an "Expect: 100-continue" field when it forwards 1667 1667 a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s).) 1668 1668 </p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1776 r1778 855 855 <t> 856 856 A successful response &SHOULD; be <x:ref>200 (OK)</x:ref> if the response 857 includes a nrepresentation describing the status, <x:ref>202 (Accepted)</x:ref>857 includes a representation describing the status, <x:ref>202 (Accepted)</x:ref> 858 858 if the action has not yet been enacted, or <x:ref>204 (No Content)</x:ref> if 859 859 the action has been enacted but the response does not include a representation. … … 1335 1335 proxy and its client has been closed, or unless the proxy itself 1336 1336 requested the generation of the 1xx response. (For example, if a 1337 proxy adds a "Expect: 100-continue" field when it forwards a request,1337 proxy adds an "Expect: 100-continue" field when it forwards a request, 1338 1338 then it need not forward the corresponding <x:ref>100 (Continue)</x:ref> 1339 1339 response(s).)
Note: See TracChangeset
for help on using the changeset viewer.