Re: HTTP/2 GREASE, Results, and Implications

Hi,

I added two simple command line flags to Chrome to trigger sending greased
HTTP/2 elements, and they are available since version 80.0.3960.0 (not on
Linux quite yet).

--http2-grease-settings adds one settings parameter with a reserved
identifier and random value to every SETTINGS frame sent (one per HTTP/2
connection).

--http2-grease-frame-type sends one frame of reserved type and random short
payload after every SETTINGS and HEADERS frame, including HEADERS frames
with END_STREAM flag set.  This is what caused problems apparently with
Cloudflare and Akamai.

Cheers,

Bence


On Mon, Nov 4, 2019 at 3:56 AM Stefan Eissing <stefan.eissing@greenbytes.de>
wrote:

> Thanks for mitigating this.
>
> > Am 01.11.2019 um 14:19 schrieb Willy Tarreau <w@1wt.eu>:
> >
> > On Fri, Nov 01, 2019 at 07:43:51AM -0400, Bence Béky wrote:
> >> Hi Willy,
> >>
> >> Yes, I agree with you.  My current plan is to make Chrome send a frame
> of
> >> reserved type
> >> * on stream 0, after the SETTINGS frame;
> >> * on non-zero streams, after each HEADERS and DATA frame that does not
> have
> >> the END_STREAM flag set;
> >> * or alternatively, after each HEADERS and DATA frame, and if the stream
> >> should be closed, then send an empty DATA frame with END_STREAM after
> the
> >> reserved frame.
> >>
> >> I think this conforms to the state transition requirements you
> summarized.
> >
> > Yes that sounds good.
> >
> >> Thank you for the guidance.  I'll keep the list posted.
> >
> > Thanks!
> > Willy
> >
>
>