Changeset 171 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

Jan 22, 2008, 4:20:31 AM (12 years ago)

Author:

julian.reschke@…

Message:

Resolve #19: as proposed in <​http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19#comment:5>

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -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>
       <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
-         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,
-         then the message-body <em class="bcp14">SHOULD</em> be ignored when handling the request.
+         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
+         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
+         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.
       </p>
       <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>&nbsp;Since draft-ietf-httpbis-p1-messaging-01
       </h2>
+      <p id="rfc.section.E.3.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19</a>&gt;: "Bodies on GET (and other) requests"
+         </li>
+      </ul>
       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
       <p>Copyright © The IETF Trust (2008).</p>