no-vary: security - cache poisoning

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Sun, 18 Jan 2026 17:03:56 +0100
• To: ietf-http-wg@w3.org
• Message-ID: <bf808d69-7de0-4f9f-a2d6-910589b36518@gmx.de>

Am 30.09.2025 um 05:20 schrieb Tommy Pauly:
> Hello HTTP,
> 
> This email starts a Working Group Last Call for draft-ietf-httpbis-no- 
> vary-search-03.
> ...

Can an intermediary cause cache poisoning in the recipients by marking 
additional parameters as irrelevant?

Best regards, Julian

Received on Sunday, 18 January 2026 16:04:04 UTC