W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: HTTP 2.0 "Upgrade" flow

From: Ilya Grigorik <ilya@igvita.com>
Date: Sun, 14 Apr 2013 15:03:00 -0700
Message-ID: <CAKRe7JEw5nQxg5uQBp44QhuCxUq37QUesx6nBDKFEAQDeUrkVg@mail.gmail.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On Sun, Apr 14, 2013 at 2:39 PM, Ilari Liusvaara <
ilari.liusvaara@elisanet.fi> wrote:

> > How does this work in light of the client/server session headers? Do we
> > skip the client session header and send the server session header,
> followed
> > by response frames? Or does the client have to wait to get the 101, and
> > then send the client session header before the connection can proceed?
>
> Of course, client has to wait for server session header or it sends
> something designed to cause things to break...


The "of course" part is not obvious. If this is indeed the intent, then we
should state it explicitly. Aka, the expected flow would be:

 >    GET /default.htm HTTP/1.1
 >    Host: server.example.com
 >    Connection: Upgrade
 >    Upgrade: HTTP/2.0

 <    HTTP/1.1 101 Switching Protocols
 <    Connection: Upgrade
 <    Upgrade: HTTP/2.0

 <    [ HTTP/2.0 server session-header
 <    [ HTTP/2.0 response frames

The client session header
(0x464f4f202a20485454502f322e300d0a0d0a4241520d0a0d0a)
is explicitly omitted in this exchange.

Correct?

ig
Received on Sunday, 14 April 2013 22:04:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC