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

Re: Extension HTTP methods

From: Anne van Kesteren <annevk@opera.com>
Date: Sun, 14 May 2006 14:19:53 +0200
To: "Jim Ley" <jim@jibbering.com>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.s9ji7fzg64w2qv@id-c0020.oslo.opera.com>

On Sun, 14 May 2006 13:59:34 +0200, Jim Ley <jim@jibbering.com> wrote:
>> There are currently some methods that can't be allowed for security  
>> reasons and because such method smay be introduced in the future as  
>> well allowing arbitrary method names does not seem like a good idea.
>
> I think you need to list these methods that cannot be used for security  
> reasons, to explain more of the motivations for this decision.  It also  
> appears to be a direct reversal of the decision at the previous f2f  
> (issue 74)  It would be good to see what had changed in between to  
> motivate the change, as there was no public discussion, other than more  
> support for having any verb.

I'm just stating the resolutions as they have been made here. Feedback  
 from implementors suggested that TRACE and CONNECT have issues and that  
future HTTP methods might become problematic (new specification released,  
servers updated, UAs are not, hole). What was raised against that is that  
it hurts adoption of new HTTP methods. That's true for all other types of  
APIs as well though. Internet Explorer 7 as opposed to Internet Explorer 6  
uses a whitelist and other browsers vendors are planning to do the same  
thing. The whitelist would contain all "safe methods" currently spreaded  
over various RFCs.

Mark Nottingham would report back if the IETF was ok with this approach or  
not.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Sunday, 14 May 2006 12:20:02 GMT

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