Tony Finch wrote:
On Wed, 6 Aug 2008, Lisa Dusseault wrote:
Before that failure, there's the problem that a GET to a HELD server requires
a custom body.
RFC 2616 says "A message-body MUST NOT be included in a request if the
specification of the request method does not allow sending an entity-body
in requests." So I think including a body in a GET request is not allowed.
That's why we have the HTTPbis WG :-)
"Bodies on GET (and other) requests" --
<http://tools.ietf.org/wg/httpbis/trac/ticket/19>
Resolution:
--- snip ---
Consensus to, in RFC2616 section 4.3:
* Change "does not allow" to "explicitly disallows", as per
http://www.w3.org/mid/64972E13-483B-4F69-94FD-F2EE516286A8(_at_)mnot(_dot_)net
* Replace 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
http://www.w3.org/mid/9C43F5AB-C3D7-4584-8F12-A9F459D3817F(_at_)gbiv(_dot_)com
--- snip --
However RFC 2616 is also not very explicit about request bodies in the
method specifications.
Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf