- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 14 Oct 2025 16:34:20 +0200
- To: ietf-http-wg@w3.org
Am 14.10.2025 um 16:22 schrieb Julian Reschke: > 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. >> ... > > I found the first part of https://www.ietf.org/archive/id/draft-ietf- > httpbis-no-vary-search-03.html#name-caching a bit hard to understand > with respect to what is replaced by what. > > See (text version): > >> 7. Caching >> >> If a cache [HTTP-CACHING] implements this specification, the >> presented target URI requirement in Section 4 of [HTTP-CACHING] is >> replaced with: >> > ... Speaking of which, RFC 9111 states in <https://greenbytes.de/tech/specs/rfc9111.html#rfc.section.4.p.3>: > Note that a cache extension can override any of the requirements listed; see Section 5.2.3. which is about Cache-Control. Was it ever considered to use Cache-Control here? (yes, I understand the parsing issues) ... in any case, a short statement why not might be good. Also: maybe make it clear upfront that the spec really defines a "Cache Extension", as described in Section 4 of RFC 9111 (and use that in Section 7, which brought me here...) (let me know if I should suggest text) Best regards, Julian
Received on Tuesday, 14 October 2025 14:34:25 UTC