W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [XHR2] PATCH Method support

From: Andres Riofrio <riofrios@gmail.com>
Date: Wed, 17 Aug 2011 11:00:12 -0700
Message-ID: <CAOmDhTNeop=fsxKbrw-ZFq6Awwk3nKKcvdaO4PSJ=BhMTO1a1Q@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Dominik Tomaszuk <ddooss@wp.pl>, public-webapps@w3.org
Correct me if I'm wrong. Changing the XHR2 spec to include other
methods in that aforementioned list has the potential to break
applications that use method names that are not all-uppercase. Is this
right?

Andres Riofrio
<riofrios@gmail.com>



On Wed, Aug 17, 2011 at 2:58 AM, Anne van Kesteren <annevk@opera.com> wrote:
> On Wed, 17 Aug 2011 11:48:19 +0200, Dominik Tomaszuk <ddooss@wp.pl> wrote:
>>
>> In Section 4.6.1 is:
>>  > If method is a case-insensitive match for CONNECT, DELETE, GET, HEAD,
>>  > OPTIONS, POST, PUT, TRACE, or TRACK subtract 0x20 from each byte in
>>  > the range 0x61 (ASCII a) to 0x7A (ASCII z).
>>
>> IMO it would be better if it contained the PATCH method.
>
> HTTP methods are case-sensitive. These are case-insensitive for this API for
> legacy reasons. We are not going to add new methods here for each new method
> defined. (That also has the potential to break applications that use e.g.
> "patch" or "Patch".)
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
>
Received on Wednesday, 17 August 2011 18:00:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT