RFC2616, section 4.3;
"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. "
GET, HEAD and DELETE do not allow for an entity-body in requests.
Granted, it's not incredibly well-specified, but are you seriously
suggesting that bodies should be allowed on GETs?
On 2006/04/21, at 3:59 PM, Julian Reschke wrote:
Mark Nottingham wrote:
[ from the big comment e-mail; raising as a separate issue, as
requested ]
The current draft says that:
"If the method is POST or PUT, then the data passed to the send()
method must be used for the entity body."
This doesn't account for other request methods that may have a
request body, e.g., PROPPATCH. Suggested text:
"Any data passed to the send() method MUST be used in the entity
body. If data is passed to send() when it is known to be incorrect
(e.g., in GET, HEAD, and DELETE requests), implementations MUST
raise an error."
Hm. Why would it be illegal (from a protocol point of view) to have
request bodies in GET, HEAD or DELETE?
Best regards, Julian
--
Mark Nottingham
[EMAIL PROTECTED]
