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

[Bug 10671] consider removing support for PUT and DELETE as form methods

From: <bugzilla@jessica.w3.org>
Date: Thu, 31 Mar 2011 13:53:19 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Q5IJL-0003SU-Dn@jessica.w3.org>

Cameron Jones <cmhjones@gmail.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #10 from Cameron Jones <cmhjones@gmail.com> 2011-03-31 13:53:16 UTC ---
(In reply to comment #9)
> My main concern is the inconsistency with GET/POST with regard to cross-origin
> requests on top of these being used far less than GET/POST. If they did not
> require the special handling the choice would be easy, but now it is not clear
> whether the additional complexity is justified.
> So in my opinion we should punt on this feature for now until it is more clear
> what exactly is needed.

i an no expert on cross-origin requests or the implementation complexity,
however i would hazard that these are being using far less than PUT and DELETE.

in response to an open question on public-html-comments, this bug has been
reviewed and is requested to be reopened based on the feedback provided in the


To paraphrase the fundamental requirement for supporting these methods on
 so that a real human is able to interact natively with a Restful system using
plain html, no ajax or other workarounds.

The form is the only user interface element capable of initiating custom HTTP
requests, without the full spectrum of methods being supported no other means
are available for interacting with HTTP-conformant services.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 31 March 2011 13:53:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:45 UTC