- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Fri, 05 Feb 2021 07:51:47 +0000
- To: Willy Tarreau <w@1wt.eu>
- 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>
-------- Willy Tarreau writes: > > 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. First, note that if your downstream understand this new extension, nothing prevents you from forwarding in a streaming fashion and leaving the XOR'ing to the next sucker in the chain. Second: Yes, that is *precisely* why I want to offer servers that option: So they have a sure-fire way to prevent sneak-peeks which they have reason to belive will get things wrong. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Friday, 5 February 2021 07:52:01 UTC