- From: Mark Baker <distobj@acm.org>
- Date: Thu, 20 Apr 2006 17:42:39 -0400
- To: "Anne van Kesteren" <annevk@opera.com>
- Cc: "Web APIs WG (public)" <public-webapi@w3.org>
I agree. I'm not aware of any HTTP extension methods which use a lower case character, so why not make "method" case-insensitive, but prescribe that it be converted to upper case in the HTTP message? Mark. On 4/18/06, Anne van Kesteren <annevk@opera.com> wrote: > > On Tue, 11 Apr 2006 23:54:43 +0200, Bjoern Hoehrmann <derhoermi@gmx.net> > wrote: > > * Web APIs Issue Tracker wrote: > >> ISSUE-75: Is method case-sensitive? > > > > We resolved that yes, the parameter is case-sensitive. This implies that > > scripts like those in the draft are essentially incorrect since there is > > no 'get' method yet. I think we should have a very visible warning for > > this in the draft then. > > So what testcases were being used? I understand that this is what HTTP > says but if implementations are different (for XMLHttpRequest at least) we > should have some reasons and arguments for making it case-sensitive. I'd > like this issue to be reopened because there's not sufficient information > on how the group reached consensus on it. (I read the minutes.) > > > -- > Anne van Kesteren > <http://annevankesteren.nl/> > <http://www.opera.com/> > > > -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca
Received on Thursday, 20 April 2006 21:42:50 UTC