Stale Cache

Serve stale cached content when the origin returns specific HTTP error responses or enters an Updating state

Stale Cache allows the CDN to serve an expired cached object when the origin is unavailable or returns a configured error condition. This provides a cached fallback during temporary origin failures without requiring the CDN to retrieve a new object.

You can manage Stale Cache in the Medianova Control Panel or via the API.

Stale content can be served only when a previously cached version of the requested object exists at the edge.

Configure Stale Cache

1

Open Stale Cache

Open your CDN Resource and select Caching.

Locate Stale Cache.

2

Select Stale Cache Triggers

Under Stale Cache Triggers, select the conditions that allow the CDN to serve stale cached content.

Available triggers include:

• error — An error occurs while communicating with the origin.

• timeout — The origin does not respond within the configured timeout.

• invalid_header — The origin returns an invalid response header.

• http_403 — The origin returns 403 Forbidden.

• http_404 — The origin returns 404 Not Found.

• http_429 — The origin returns 429 Too Many Requests.

• http_500 — The origin returns 500 Internal Server Error.

• http_502 — The origin returns 502 Bad Gateway.

• http_503 — The origin returns 503 Service Unavailable.

• http_504 — The origin returns 504 Gateway Timeout.

• updating — Stale content can be served while the cached object is being updated.

When any selected trigger occurs, the CDN can serve an available stale cached version of the requested object.

3

Save the Configuration

Select Save in the pending changes bar.

Review the pending changes and confirm the update to apply the configuration to the CDN Resource.

Stale Cache Behavior

Stale Cache uses an existing expired cached object as a fallback when one of the configured triggers occurs.

The CDN does not create a stale object when no cached version exists. In that case, Stale Cache cannot provide a cached fallback for the request.

When the configured stale condition no longer applies, normal cache behavior resumes according to the resource's caching configuration.

Stale Cache can keep content available during temporary origin failures, but the response may contain an older version of the object. Select triggers according to the freshness requirements of your content.