W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2010

Re: #233: Is * usable as a request-uri for new methods?

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 23 Oct 2010 09:47:18 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <9CF85F18-254E-43C0-8D7A-8CE384AE0ABA@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>
I think we can leave it out for now; it's pretty obvious to someone looking at the * form, and I imagine we're going to do at least one more sweep through the specs for such considerations before we're done.

Thanks,


On 22/10/2010, at 11:46 PM, Julian Reschke wrote:

> On 22.10.2010 00:29, Mark Nottingham wrote:
>> OK, marking for incorporation into -12.
> 
> So, in P1 we have:
> 
> -- snip --
> The asterisk "*" ("asterisk form") means that the request does not apply to a particular resource, but to the server itself, and is only allowed when the method used does not necessarily apply to a resource. One example would be
> 
> OPTIONS * HTTP/1.1
> -- snip --
> 
> 
> This would become:
> -- snip --
> The asterisk "*" ("asterisk form") means that the request does not apply to a particular resource, but to the server itself. This is only allowed for the OPTIONS method. Thus, the only valid example is
> 
> OPTIONS * HTTP/1.1
> -- snip --
> 
> In P2, we *could* add it to the Considerations for new Methods. Do we need to?
> 
> Best regards, Julian
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Friday, 22 October 2010 22:47:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:30 GMT