3 replies

Cache API Expires After 120m

Hi guys,

I have a worker that fetch from JSON from origin and supposed to cache it "permanently" in edge. Below is the sample code:

const originUrl = new URL(req.url);
originUrl.searchParams.append('t', Date.now().toString()); // Ensure Hitting Origin
const originRes = await fetch(originUrl.toString(), req);

// ... other checks to make sure origin response is 200.

originRes.headers.delete('Cache-Control');
originRes.headers.append('Cache-Control', 'public, max-age=31536000, immutable');

cache.put(cacheKey, originRes);

const originUrl = new URL(req.url);
originUrl.searchParams.append('t', Date.now().toString()); // Ensure Hitting Origin
const originRes = await fetch(originUrl.toString(), req);

// ... other checks to make sure origin response is 200.

originRes.headers.delete('Cache-Control');
originRes.headers.append('Cache-Control', 'public, max-age=31536000, immutable');

cache.put(cacheKey, originRes);

Cam confirm that the above code is cached in edge with

CF-Cache-Status

CF-Cache-Status

and

Age

Age

of the subsequence response. The "Browser Cache TTL" of the zone is also configured to "Respect Existing Headers" and that the

Cache-Control

Cache-Control

is the overwritten one with 1 year TTL in the worker.

However, the cache will get deleted from edge as soon as it hit 7.2k Age, or 120m, which is the default edge TTL for code 200.

Can I check if this is a limitation with Cache API or is there any other config that I missed out?

Thank you.

Cache API Expires After 120m

Hi guys,

I have a worker that fetch from JSON from origin and supposed to cache it "permanently" in edge. Below is the sample code:

const originUrl = new URL(req.url);
originUrl.searchParams.append('t', Date.now().toString()); // Ensure Hitting Origin
const originRes = await fetch(originUrl.toString(), req);

// ... other checks to make sure origin response is 200.

originRes.headers.delete('Cache-Control');
originRes.headers.append('Cache-Control', 'public, max-age=31536000, immutable');

cache.put(cacheKey, originRes);

const originUrl = new URL(req.url);
originUrl.searchParams.append('t', Date.now().toString()); // Ensure Hitting Origin
const originRes = await fetch(originUrl.toString(), req);

// ... other checks to make sure origin response is 200.

originRes.headers.delete('Cache-Control');
originRes.headers.append('Cache-Control', 'public, max-age=31536000, immutable');

cache.put(cacheKey, originRes);

Cam confirm that the above code is cached in edge with

CF-Cache-Status

CF-Cache-Status

and

Age

Age

of the subsequence response. The "Browser Cache TTL" of the zone is also configured to "Respect Existing Headers" and that the

Cache-Control

Cache-Control

Cache API Expires After 120m

Similar Threads

Cache API Expires After 120m

Similar Threads

Similar Threads

Similar Threads