W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2019

Re: HTTP/2 GREASE, Results, and Implications

From: Willy Tarreau <w@1wt.eu>
Date: Thu, 31 Oct 2019 19:55:43 +0100
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Mike Bishop <mbishop@evequefou.be>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20191031185543.GB30937@1wt.eu>
On Thu, Oct 31, 2019 at 06:10:33PM +0000, Lucas Pardue wrote:
> On Thu, Oct 31, 2019 at 5:49 PM Mike Bishop <mbishop@evequefou.be> wrote:
> > Upon further investigation, it appears that Akamai hosts most of the sites
> > where the connection gets closed, and Cloudflare hosts the sites which
> > close the stream but leave the connection open (I'm guessing, from what the
> > dev tools show).  Given that we're both represented here, it seems likely
> > that we should be able to drive some internal bugfixes and improve the
> > state of the ecosystem.
> >
> It's possible the Cloudflare closures are related to the client-oriented
> half-closed issue that Willy and Bence have discussed.

Maybe, but regardless, if we have to accept any frame type, half-closed
makes no difference. For haproxy I still purposely decided not to accept
to create a new stream from a unknown frame type (i.e. a frame type
designating an idle stream must be either HEADERS or PRIORITY as stated
in the spec). Because if we start to let such things pass through, we
can't really count on the other end's behavior for subsequent frames :-/

> We'd be happy to
> coordinate with other members of the group on a rerun of the experiment in
> order to come to a more definitive answer.

It would be nice to retest at world scale and be a bit more prepared to
assist users who report breakage.

Received on Thursday, 31 October 2019 18:55:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:43 UTC