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

Re: XMLHTTPRequest Issue on behaviour when method not supported

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 25 May 2006 10:43:12 +0200
To: Jim Ley <jim@jibbering.com>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-id: <op.s93miakp64w2qv@id-c0020.oslo.opera.com>

On Wed, 24 May 2006 16:41:53 +0200, Jim Ley <jim@jibbering.com> wrote:
> A valid HTTP method name. The GET, POST, PUT, DELETE and HEAD values  
> MUST be supported
>
> Nowhere is the behaviour defined for what happens if the methods are not  
> supported, the current behaviour in those user agents who only support a  
> couple of methods - that of silently transformed into GET, is not much  
> use, and I would say very wrong.
>
> Please change it to throw an exception on open if you use a method which  
> is not defined, or alternatively provide a property which is the actual  
> method going to be used, preferably the exception.

I'd like to defer this until the whole method discussion has been sorted  
out. Consider it noted though.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Thursday, 25 May 2006 08:44:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:55 GMT