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, 5.5 Extending HTTP/2

From: Yutaka Hirano <yhirano@google.com>
Date: Fri, 18 Jul 2014 02:32:01 +0900
Message-ID: <CABihn6H63AZ3mRxmUM1KxK_QFUozMDiRpFSs7S0_R25QzPzsgA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTPBIS working group mailing list <ietf-http-wg@w3.org>
>
> > To do so, the server must know the capability when the handshake request
> > arrives.
> The capability of the client is apparent when a request for :scheme =
> "ws[s]" arrives.

The capability of the client is apparent, but the server should know if all
intermediaries support WS over HTTP/2.
An intermediary can transfer :scheme = ws[s] request without understanding
WS over HTTP/2.
Am I missing something?



On Fri, Jul 18, 2014 at 2:08 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 17 July 2014 10:06, Yutaka Hirano <yhirano@google.com> wrote:
> > So I plan to allow the client to start an opening handshake without
> knowing
> > that the HTTP/2 connection is capable of WS.
> > If it is not capable of WS, the client may retry connecting with the
> native
> > WS.
>
> You can do that; the failure mode is no worse, but you can succeed faster.
>
> > To do so, the server must know the capability when the handshake request
> > arrives.
>
> The capability of the client is apparent when a request for :scheme =
> "ws[s]" arrives.
>
Received on Thursday, 17 July 2014 17:32:28 UTC

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