demo · v135
One cache entry, many query strings
The use case from the explainer: tracking parameters (utm_source, fbclid) and reorder-tolerant pagination (?page=2&sort=desc vs ?sort=desc&page=2) used to bust the cache, even though the response was identical. No-Vary-Search tells the disk cache which params to ignore. Define a header on the left, hit URLs on the right, watch the same cache entry serve them all.
simulated disk cache
server response header
HTTP/1.1 200 OK No-Vary-Search: