Stale Cache

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

Stale Cache allows CDN edge servers to deliver the last cached version of an object when the origin becomes temporarily unavailable. This includes conditions such as 500–504 errors, invalid headers, timeouts, forbidden responses, or an Updating status. Enabling Stale Cache helps maintain availability and ensures continuity of service during short-term origin instability.

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

Log in to the Medianova Control Panel, select a CDN resource in the CDN section, and navigate to the Stale Cache.

Configure Stale Cache

This workflow defines which origin responses allow the CDN to serve stale cached content.

1

Select stale cache triggers

Choose one or more conditions from the trigger list. Stale content will be served when any selected condition occurs.

Supported triggers in the Medianova Control Panel:

• error — Generic error indicator returned by the origin system.

• timeout — The CDN did not receive a timely response from the origin.

• invalid_header — The origin returned malformed or unexpected HTTP headers.

• http_500 — Internal Server Error.

• http_502 — Bad Gateway.

• http_503 — Service Unavailable.

• http_504 — Gateway Timeout.

• http_403 — Forbidden.

• http_404 — Not Found.

• http_429 — Too Many Requests (rate limit).

• updating — The origin is in an update/maintenance state.

2

Save the configuration

Select Submit to apply all changes.

• Stale content is served only if a cached version already exists at the edge.

• Any selected trigger can activate stale delivery.

• When the origin becomes healthy again, normal cache rules resume automatically.

• Stale Cache does not refresh or regenerate content; it only delivers the most recent cached copy.

• This feature is intended for temporary failures, not extended outages.

FAQ

What happens if no triggers are selected? Stale content is never served.

Will Stale Cache fetch new content? No. It serves only what is already cached.

Does enabling all triggers hide origin problems? It may delay visibility of backend issues. Select triggers based on operational strategy.

Does TTL affect stale delivery? TTL defines freshness; stale delivery allows fallback after TTL when origin issues occur.