We intend to prototype support for the No-Vary-Search HTTP caching extension in Firefox.
*Specification* No-Vary-Search (IETF httpbis): https://httpwg.org/http-extensions/draft-ietf-httpbis-no-vary-search.html *Summary* The No-Vary-Search specification defines a new HTTP response header, No-Vary-Search, that allows servers to declare which URL query parameters should be ignored when matching cache entries. This enables the browser to serve a cached response for a URL even when query parameters differ, as long as the server has declared those parameters do not affect the response. For example, given the response header: No-Vary-Search: params=("utm_source" "utm_medium" "utm_campaign") If the browser has a cached response for https://example.com/article, it will also serve that cached response for: https://example.com/article?utm_source=email, and https://example.com/article?utm_source=social&utm_medium=paid&utm_campaign=summer But not for https://example.com/article?ref=homepage Because ref is not declared as ignorable, it still causes a cache miss. *Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=2037149 *Mozilla Standards Position*: https://github.com/mozilla/standards-positions/issues/717 (Positive) *Other Browsers* Chrome: Shipped (Chrome 141, HTTP disk cache) Safari: No position ( https://github.com/WebKit/standards-positions/issues/106) *Platform Coverage* All *Web Platform Tests* https://wpt.fyi/results/?label=master&label=experimental&aligned&q=no-vary-search -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CA%2BnBSt_OLp0k2Y%2BdsNLSULNBLP68fswu_ZQ7CGmQ6jAQHr23tw%40mail.gmail.com.
