- From: Willy Tarreau <w@1wt.eu>
- Date: Fri, 23 Oct 2020 16:46:25 +0200
- To: Bence Béky <bnc@chromium.org>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, Mike Bishop <mbishop@evequefou.be>, Eric Lawrence <Eric.Lawrence@microsoft.com>
On Fri, Oct 23, 2020 at 10:42:05AM -0400, Bence Béky 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. Cheers, Willy
Received on Friday, 23 October 2020 14:46:45 UTC