On Mon, 24 Apr 2006 21:15:36 +0200, Mark Baker [EMAIL PROTECTED] wrote:
On 4/22/06, Maciej Stachowiak [EMAIL PROTECTED] wrote:
Current implementations silently ignore the body in this case.
FWIW, I decided to test this. As it turns out, IE and Firefox on
WinXP pass bodies on all methods
Maciej Stachowiak wrote:
On Apr 21, 2006, at 9:33 AM, 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
Mark Nottingham wrote:
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
On 2006/04/22, at 7:45 AM, Mark Baker wrote:
On 4/21/06, Mark Nottingham [EMAIL PROTECTED] wrote:
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.
Right.
On 4/22/06, Mark Nottingham [EMAIL PROTECTED] wrote:
I do agree that HTTP isn't very clear on this matter, but I couldn't
find any immediately apparent discussion in the WG. Do you have a ref?
AFAIK, this is the latest discussion on the topic, which has some
links to previous discussions;
[ 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,
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
