Cache coherence
Inspect current-origin CacheStorage and service-worker state read-only, or compare user-supplied release markers without claiming CDN freshness.
Inspect this browser’s application cache surfaces
Read only this origin’s CacheStorage inventory and service-worker registration/control state. Cache names, request URLs, response bodies and worker script addresses are never shown or exported. This performs no deliberate cache write or deletion. If another tab deletes a cache during inspection, CacheStorage.open may recreate an empty namespace; do not inspect concurrently with cache maintenance.
The browser’s ordinary HTTP cache, proxy caches and CDN edge storage are not accessible through CacheStorage. Counts alone cannot prove cache freshness or a version match.
- Cache limit
- 8
- Per-cache observation limit
- 2048
- Observation deadline
- 3 seconds
- Traffic
- No test requests
Compare declared release markers
For an application you operate, provide release identifiers independently obtained from its currently loaded shell, service-worker release and edge deployment. This is an unverified manual comparison. It does not retrieve versions from a network endpoint.
At least two declared markers are required. No marker value is copied to the report or export; only counts, equality results and uncertainty notes are retained.
Coherence limitations
A service-worker cache can contain old files even when no worker controls this tab. A successful manual release-marker comparison is not proof that browsers are serving the same bytes as the CDN or origin. Use Asset Integrity to check the current platform’s build files, and Resource Waterfall for browser-exposed request timing. Neither provides a CDN edge consistency guarantee.