*Summary:* Today, two URLs that differ only in query parameters irrelevant to the response content (https://example.com/article?ref=homepage and https://example.com/article?ref=sidebar) are treated as separate cache entries, causing redundant network requests even when the server returns identical content. The No-Vary-Search HTTP response header lets servers declare which query parameters are irrelevant to the response, allowing the browser to reuse cached entries across those URL variants. This reduces unnecessary network traffic and improves page load performance for users, with no changes required from web developers beyond a single response header. No-Vary-Search is also used extensively by the Speculation Rules API, where it allows speculative prefetches to match navigations to URLs that differ only in declared-irrelevant query parameters.
*Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=2037149 *Specification: * https://httpwg.org/http-extensions/draft-ietf-httpbis-no-vary-search.html *Standards Body: * IETF (httpbis) *Platform Coverage: * All *Preference: * network.http.no-vary-search.enabled *DevTools Bug: * N/A *Extensions Bug: * N/A *Use Counter: * N/A *Standards-Positions Discussion:* https://github.com/mozilla/standards-positions/issues/717 (Positive) *Other Browsers: * Blink: Shipped (Chrome 141) WebKit: No position ( https://github.com/WebKit/standards-positions/issues/106) *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-zOw%3D2_r%2Bzh0JdCAd9uOxPbK%2Biw8Mu4oDikQtQ%2B1Mrqg%40mail.gmail.com.
