- From: Willy Tarreau <w@1wt.eu>
- Date: Fri, 5 Feb 2021 08:46:02 +0100
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Adrien de Croy <adrien@qbik.com>, Greg Wilkins <gregw@webtide.com>, Stefan Eissing <stefan.eissing@greenbytes.de>, Ryan Sleevi <ryan-ietf@sleevi.com>, Martin Thomson <mt@lowentropy.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On Fri, Feb 05, 2021 at 07:39:35AM +0000, Poul-Henning Kamp wrote: > -------- > Adrien de Croy writes: > > > not in my experience. > > Good for you! > > But it is the number #1 thing on peoples wishlist whenever they ask about > trailers in Varnish Cache. > > > What sort of metadata is it envisioned would require waiting until the > > end of transmission to set and be based on the entire content? > > Cache-Control, Set-Cookies, and the multitude of private headers people > use for CDN and walled-garden applications. > > > We've had > > discussions in the past about clients sniffing response message bodies > > and it was decided it was a bad thing for security reasons, but I think > > everyone still does it or the internet breaks. > > Which is *precisely* why I propose we give the server the option > to XOR scramble the body until the metadata is ready. No please Poul-Henning, really please, no more addition of such horrors that we had to deal with in WebSocket. It serves no purpose and prevents anyone along the chain from efficiently processing the contents, including but not limited to, H1<->H2 translation, compression, inspection, etc. Please do not add ugliness on top of ugly things, you usually have much better and cleaner proposals, let's get back to deployed standards and stick to what works where relevant :-/ Willy
Received on Friday, 5 February 2021 07:46:31 UTC