Managing caches

The global caches object, covering the default cache and how to open named caches.

Default cache

The caches.default API follows the web browsers’ Cache API interface closely. It gives you a single, unnamed cache shared across requests.

await caches.default.match(request);

Named caches

You may create and manage additional Cache instances via the caches.open method. Named caches are useful when you want to version cache contents (e.g. cache:v1, cache:v2) so a deploy can switch over cleanly.

const cache = await caches.open("cache:v1");
await cache.match(request);

Note: When using the Cache API, avoid overriding the hostname in cache requests, as this can lead to unexpected behaviour when using multiple domains associated with a PullZone.

// recommended approach: use current request url
const url = new URL(request.url);

const cache = await caches.open("cache:v1");
const response = await cache.match(`${url.origin}/example.html`);

References

• Reading & writing: the match, put, and delete method reference.
• Examples: end-to-end recipes using named and default caches.
• Cache API overview: regional behavior, limitations, and API surface.