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

Re: H2 vs responses which should not carry any payload

From: Willy Tarreau <w@1wt.eu>
Date: Fri, 23 Oct 2020 16:46:25 +0200
To: Bence Bky <bnc@chromium.org>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Mike Bishop <mbishop@evequefou.be>, Eric Lawrence <Eric.Lawrence@microsoft.com>
Message-ID: <20201023144625.GA5311@1wt.eu>
On Fri, Oct 23, 2020 at 10:42:05AM -0400, Bence Bky wrote:
> Hi Willy,
> Sorry, my previous e-mail was incorrect.  Chrome did run into some
> issues with buggy servers, and a fix to those servers has been
> deployed since.  Separately, the same bug is thought to exist in
> WinHTTP.  However, WinHTTP is a client-only stack, so this should only
> affect responses, not requests.  Which is exactly what you are worried
> about.

OK, thanks to you and Mike for the details :-)

This comforts me in the idea that we really need to do our best to
consider a bit of semantics when serializing the response and emit
ES immediately.

Received on Friday, 23 October 2020 14:46:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 23 October 2020 14:46:46 UTC