← back to v141 · no-vary-search-support-for-the-http-disk-cache
conformance · v141
v141 · no-vary-search-support-for-the-http-disk-cache — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
fetch-exists |
fetch is the API through which No-Vary-Search-controlled cache hits are observed in the page. | typeof | … | |
request-cache-default |
Request supports the cache init member ('default' etc.); No-Vary-Search interacts with the HTTP disk cache layer that this surface controls. | script | … | |
cachestorage-exists |
caches (CacheStorage) is exposed; No-Vary-Search is also acceptable in service-worker Cache lookups in some implementations. | exists | … | |
performance-resource-timing |
PerformanceResourceTiming entries expose transferSize/encodedBodySize, the surfaces by which cache hits surface in the page. | script | … | |
headers-getsetcookie |
Headers.prototype.get is callable; the No-Vary-Search response header is read via the standard fetch Headers API. | script | … | |
url-search-params-iterable |
URLSearchParams is iterable; No-Vary-Search semantics are defined over the URL's query parameter set. | script | … |