W3C home > Mailing lists > Public > public-html-comments@w3.org > March 2011

Re: PUT and DELETE methods in form@method

From: Cameron Heavon-Jones <cmhjones@gmail.com>
Date: Wed, 30 Mar 2011 15:02:52 +0100
Cc: "T.J. Crowder" <tj@crowdersoftware.com>, Dominik Tomaszuk <ddooss@wp.pl>, public-html-comments@w3.org
Message-Id: <AA1692F8-8098-4D80-B7DE-781702056D94@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Existing servers don't do this for PUT or DELETE but then existing servers don't currently support these methods from forms anyway.

Servers don't need special cases for requests from forms, they need special cases based on what content type the agent says it can handle.


On 30/03/2011, at 2:39 PM, Julian Reschke wrote:

> On 30.03.2011 15:20, Cameron Heavon-Jones wrote:
>> why can't a 201 just include some body content like a 200? This would
>> allow for any response status to include html content for rendering the
>> response to the user. The response content may not be available through
>> any other uri of method but it seems like thats the way it should work.
>> cam
> Well,
> existing servers do not do this for PUT and DELETE, as existing clients do only care about the status.
> So servers would need to special-case requests from HTML forms; not good.
> BR, Julian
Received on Wednesday, 30 March 2011 14:03:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:27 UTC