From 76e346f068ec25a28717d5459145b16b2a886896 Mon Sep 17 00:00:00 2001 From: Julian Reschke Date: Tue, 14 Oct 2025 15:26:09 +0100 Subject: [PATCH] no-vary: updating CACHING (fixes #3285) --- draft-ietf-httpbis-no-vary-search.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/draft-ietf-httpbis-no-vary-search.md b/draft-ietf-httpbis-no-vary-search.md index 65a216d8d0..b8279865cf 100644 --- a/draft-ietf-httpbis-no-vary-search.md +++ b/draft-ietf-httpbis-no-vary-search.md @@ -419,11 +419,15 @@ So, for example, given any non-default value for `No-Vary-Search`, such as `No-V # Caching {#caching} -If a cache {{HTTP-CACHING}} implements this specification, the presented target URI requirement in {{Section 4 of HTTP-CACHING}} is replaced with: +If a cache {{HTTP-CACHING}} implements this specification, the presented target URI requirement in {{Section 4 of HTTP-CACHING}}: -* one of the following: - * the presented target URI ({{Section 7.1 of HTTP}}) and that of the stored response match, or - * the presented target URI and that of the stored response are equivalent modulo search variance ({{comparing}}), given the variance obtained ({{obtain-a-url-search-variance}}) from the stored response. +> the presented target URI (Section 7.1 of [HTTP]) and that of the stored response match, and +{:quote} + +is replaced with: + +> the presented target URI (Section 7.1 of [HTTP]) and that of the stored response match or are equivalent modulo search variance, and +{:quote} Cache implementations MAY fail to reuse a stored response whose target URI matches _only_ modulo URL search variance, if the cache has more recently stored a response which: