W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

i19 - bodies on GET -- round 2

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 15 May 2007 16:59:19 +1000
Message-Id: <0B0A6372-C332-40A1-AF9D-252B8B1EF0BA@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>

Section 4.3;

> 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 MUST NOT be included  
> in a request if the specification of the request method (section  
> 5.1.1) does not allow sending an entity-body in requests. A server  
> SHOULD 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 SHOULD be ignored when handling the  
> request.

I propose both:

* Changing "does not allow" to "explicitly disallows", as per [1]
* Replacing the last sentence with: [[[  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 SHOULD either ignore the message-body or respond with  
an appropriate error message (e.g., 413).  A proxy or gateway, when  
presented the same request, SHOULD either forward the request inbound  
with the message-body or ignore the message-body when determining a  
response. ]]], as per [2]

1. http://www.w3.org/mid/64972E13-483B-4F69-94FD-F2EE516286A8@mnot.net
2. http://www.w3.org/mid/9C43F5AB-C3D7-4584-8F12-A9F459D3817F@gbiv.com

Mark Nottingham     http://www.mnot.net/
Received on Tuesday, 15 May 2007 06:59:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:42 UTC