- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 2 Mar 2025 13:21:55 +0100
- To: ietf-http-wg@w3.org
On 02.03.2025 10:25, Julian Reschke wrote: > On 01.03.2025 12:57, Amos Jeffries wrote: >> ... >> I have implemented test changes for Squid to support this feature set. >> ... > > Very good. > >> Some editorial nits: >> >> Section 2.4 requires normalization of the content for cache key, with >> several suggestions/requirements: >> >> * The first one mentions content encoding but does not name the >> relevant header(s) (Content-Encoding, Transfer-Encoding) as the other >> bullet points do. > > Just Content-Encoding, right? T-C should be orthogonal to caching. > ... Ah, I see where you're coming from. Yes, transfer encodings, when present, would be removed first. But those are specific to HTTP/1.1, they happen at a lower level in the protocol stack. They aren't even mentioned in the HTTP Caching spec (RFC 9111). Best regards, Julian
Received on Sunday, 2 March 2025 12:21:59 UTC