Serve Stale Content limits on origin error codes and Cache-Control interaction

Answer

Cloudflare treats a cached 404 as a fresh response (not a stale candidate) as long as its TTL has not expired; it will not serve a previously cached 200 OK in place of a 404 unless the origin returns a 5xx error or times out.

When the dashboard Serve Stale Content toggle is disabled, the stale‑if-error Cache‑Control directive can still trigger stale serving, but only for errors that Cloudflare considers “origin failure” (5xx or timeout). A 404 does not satisfy that condition, so stale‑if-error has no effect on a 404 response.

Confirmed facts

• Serve Stale Content (global setting) applies to 5xx server errors and origin timeouts.
• A cached 404 is considered a fresh asset; it is not a stale candidate for replacement.
• The stale‑if-error directive is evaluated per‑response and works independently of the global toggle.
• Cache Rules have higher precedence than legacy Page Rules/Cache settings when both are present.

Likely explanation / nuances

Because Cloudflare distinguishes between background revalidation (stale‑while‑revalidate) and failure recovery (stale‑if-error), the latter only activates when the origin is deemed unavailable. A 4xx status is interpreted as an intentional client‑error signal, not a failure, so the directive is ignored for those responses. Plan‑level entitlements affect the maximum stale‑serving window (e.g., Free plan limited to 1 hour, Enterprise can be longer), but they do not change the 4xx vs 5xx classification.

Steps to reconcile Cache Rules and legacy settings

1. Disable any legacy Page Rule or Cache setting that attempts to control stale serving, or set it to match the intended Cache Rule.
2. Create a Cache Rule that matches the desired URL pattern and set Cache‑Control: stale‑if-error=... (or use the rule’s “Serve stale content” action).
3. Verify that the rule’s action is enabled; the global dashboard toggle can remain off if you rely solely on the rule.
4. If you need to serve stale on 4xx responses, you must modify the origin (or use a Worker) to return a 5xx or to inject a stale‑if-error header that Cloudflare will treat as a failure signal.
5. Check your plan’s maximum stale duration (e.g., via the dashboard → Caching → Configuration) and ensure the stale‑if-error value does not exceed it.

Missing diagnostic detail

If you are on a Free or Pro plan and need to serve stale longer than the plan‑allowed maximum, please confirm your current plan tier; this may change the recommendation to upgrade or to adjust the stale‑if-error value.