W3C home > Mailing lists > Public > public-webapi@w3.org > June 2006

ISSUE-75 proposal

From: Mark Baker <distobj@acm.org>
Date: Wed, 28 Jun 2006 23:25:33 -0400
Message-ID: <c70bc85d0606282025j5254fda7kba741d5ea6c72e9d@mail.gmail.com>
To: "Web APIs WG (public)" <public-webapi@w3.org>

This is the HTTP method case issue, and I propose the following text
to resolve it.  In place of the description of "method of type
DOMString" in section 2 of XMLHttpRequest, I suggest;

An HTTP method name.  If it is one of "get", "put", "post", "delete",
or "head" (in lower or mixed case), then implementations MUST convert
it to upper case when using it to construct the HTTP message.
Otherwise, it SHOULD be used in the HTTP message as-is.

I believe this accomodates the needs of those who fear unnecessary
HTTP profiling (by fixing the number of methods which are uppercased -
props to mnot), those concerned about existing agents which uppercase
everything (hence "SHOULD"), and those concerned about compatibility
with existing content (by calling out the lowercase methods which
these scripts likely use).


Received on Thursday, 29 June 2006 03:25:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:21 UTC