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: Michael Sweet <msweet@apple.com>
Date: Fri, 25 Jul 2014 00:59:39 -0400
Message-id: <61CD6B6E-852E-4730-9488-7F32937B0647@apple.com>
Cc: Mark Nottingham <mnot@mnot.net>, Martin Thomson <martin.thomson@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
To: Julian Reschke <julian.reschke@gmx.de>
HTTP Upgrade

Sent from my iPad

> On Jul 24, 2014, at 1:43 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
>> 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 Friday, 25 July 2014 05:00:12 UTC

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