Changeset 171
- Timestamp:
- 22/01/08 12:20:31 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r170 r171 1236 1236 <p id="rfc.section.4.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p> 1237 1237 <p id="rfc.section.4.3.p.5">The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field 1238 in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) does not allow sending an entity-body in requests. A server <em class="bcp14">SHOULD</em> read and forward a message-body on any request; if the request method does not include defined semantics for an entity-body, 1239 then the message-body <em class="bcp14">SHOULD</em> be ignored when handling the request. 1238 in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length 1239 and a method that does not define any semantics for that request message-body, then an origin server <em class="bcp14">SHOULD</em> either ignore the message-body or respond with an appropriate error message (e.g., 413). A proxy or gateway, when presented 1240 the same request, <em class="bcp14">SHOULD</em> either forward the request inbound with the message-body or ignore the message-body when determining a response. 1240 1241 </p> 1241 1242 <p id="rfc.section.4.3.p.6">For response messages, whether or not a message-body is included with a message is dependent on both the request method and … … 2441 2442 <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a> Since draft-ietf-httpbis-p1-messaging-01 2442 2443 </h2> 2444 <p id="rfc.section.E.3.p.1">Closed issues: </p> 2445 <ul> 2446 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19</a>>: "Bodies on GET (and other) requests" 2447 </li> 2448 </ul> 2443 2449 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 2444 2450 <p>Copyright © The IETF Trust (2008).</p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r170 r171 1441 1441 the request's message-headers. A message-body &MUST-NOT; be included in 1442 1442 a request if the specification of the request method (&method;) 1443 does not allow sending an entity-body in requests. A server &SHOULD; 1444 read and forward a message-body on any request; if the request method 1445 does not include defined semantics for an entity-body, then the 1446 message-body &SHOULD; be ignored when handling the request. 1443 explicitly disallows an entity-body in requests. 1444 When a request message contains both a message-body of non-zero 1445 length and a method that does not define any semantics for that 1446 request message-body, then an origin server &SHOULD; either ignore 1447 the message-body or respond with an appropriate error message 1448 (e.g., 413). A proxy or gateway, when presented the same request, 1449 &SHOULD; either forward the request inbound with the message-body or 1450 ignore the message-body when determining a response. 1447 1451 </t> 1448 1452 <t> … … 4157 4161 <section title="Since draft-ietf-httpbis-p1-messaging-01"> 4158 4162 <t> 4163 Closed issues: 4164 <list style="symbols"> 4165 <t> 4166 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19"/>: 4167 "Bodies on GET (and other) requests" 4168 </t> 4169 </list> 4159 4170 </t> 4160 4171 </section>
Note: See TracChangeset
for help on using the changeset viewer.