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

Re: PUT and DELETE methods in 200 code

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 04 Apr 2011 19:13:46 +0200
Message-ID: <4D99FC4A.1060701@gmx.de>
To: Cameron Heavon-Jones <cmhjones@gmail.com>
CC: mike amundsen <mamund@yahoo.com>, public-html@w3.org, public-html-comments@w3.org, ietf-http-wg@w3.org, Dominik Tomaszuk <ddooss@wp.pl>
On 04.04.2011 19:03, Cameron Heavon-Jones wrote:
> Feedback on: Supporting PUT and DELETE with HTML FORMS @ 2011-04-04
> 1.2. Assumptions
> I think that DELETE requires the same support as PUT and POST. The requirement for this was posted to public-html-comments:
> http://lists.w3.org/Archives/Public/public-html-comments/2011Apr/0020.html
> I would suggest that DELETE uses the same URI encoding rules as for GET by default, with the option of also being allowed to be encoded in the same enctypes as for PUT and POST. This will allow for a DELETE request using query parameters to be constructed through a form or, for the other enctypes, for the DELETE request to be embedded with configurable attributes.
> For example, it would be great to be able to generate a DELETE request to a uri like:
> <form action="http://example.org/user"” method=”delete” if-match="*">
>    <input name="hat-size" type="text" value="" />
>    <input type="submit" />
> </form>	
> DELETE user?hat-size=small HTTP/1.1
> Host: www.example.org

What's the use case for the "other" encoding (form field in payload)???

> ...

Best regards, Julian
Received on Monday, 4 April 2011 17:14:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:51 UTC