W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 8.1.2.1 Request Header Fields | Re: draft-ietf-httpbis-http2-latest, 5.5 Extending HTTP/2

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 24 Jul 2014 19:43:29 +0200
Message-ID: <53D145C1.4050801@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: Martin Thomson <martin.thomson@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
On 2014-07-24 19:26, Mark Nottingham wrote:
> We already say “The asterisk-form of request-target is only used for a server-wide OPTIONS request”. <http://httpwg.github.io/specs/rfc7230.html#rfc.section.5.3.4>

True, but not fully sufficient, as long as people disagree with what 
"server-wide" means... I've seen attempts to use "OPTIONS *" both when 
revising WebDAV and when introducing PATCH, and it took a lot of energy 
to prevent it.

Do we have an example for use of "OPTIONS *" that actually makes sense?

Best regards, Julian
Received on Thursday, 24 July 2014 17:47:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:09 UTC