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: Tue, 29 Jul 2014 08:40:07 -0400
Cc: ietf-http-wg@w3.org
Message-id: <DF8474DC-4BA2-44F4-9533-A609AC3F4C06@apple.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Amos,

On Jul 29, 2014, at 7:04 AM, Amos Jeffries <squid3@treenet.co.nz> wrote:
> ...
> ... "http://some.host" being absolute form, and the request under
> discussion here being OPTIONS.

Right, for a proxied OPTIONS request, the special casing in RFC 7230 section 5.3.4 covers mapping "OPTIONS http://some.host" to "OPTIONS *".  But you don't proxy OPTIONS requests with "Connection: upgrade".

But my original point was that "OPTIONS *" is used to upgrade the connection to the endpoint, with "*" meaning "the server as a whole". You may not like "*", but more than 10^9 existing clients have software that uses it for secure printing, and its use has been a proposed standard for a long time.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair



Received on Tuesday, 29 July 2014 12:40:42 UTC

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