Back to notes

Note by Niko

Edge cache misbehaviour: when Cloudflare caching causes stale or missing pages

By Niko April 28, 2026 2 min read

When Cloudflare caching serves stale content or never caches the page that should be fast, the real issue is usually in the rule logic, not the CMS.

Related service

This note supports the Cloudflare WAF / bot / 403 / 1020 access fixes sprint lane.

View service

Content delivery networks like Cloudflare are designed to improve performance and reduce load on origin servers. Yet misconfigured cache rules, page rules, or Workers can produce the opposite effect: stale content that never updates or pages that never get cached at all.

When changes fail to appear in search results or users see outdated pages, it is worth examining the edge cache before blaming the CMS.

Isolate the cache behavior first

Before changing anything, determine how the cache is behaving:

  • Which exact URL or path is failing?
  • Does the problem affect everyone or only some users?
  • Are you seeing a HIT, MISS, or BYPASS in cf-cache-status?

If the answer is "only some traffic, only some paths, after a recent rule change," that already points you toward the edge configuration rather than the origin.

Common causes of cache misbehaviour

Most valid-content caching incidents come from a short list:

  • page rules that are too broad and cache HTML that should not be cached
  • origin or middleware headers that unintentionally send Cache-Control: no-cache
  • Workers or firewall rules that bypass cache for certain user agents or paths
  • TTLs that are so long that updated content does not propagate quickly
  • staging or preview cache rules leaking into production during deployments

The first useful move is comparing the failing request against the rule logic, not clearing caches at random.

Validate and correct the rule set

After identifying the problematic rule or header, cleanup often involves:

  1. refining page rules so Cache Everything only applies where it should
  2. ensuring the application sends the right Cache-Control headers for cacheable responses
  3. purging specific URLs or tags instead of running full cache purges
  4. testing both edge and origin responses to confirm the CDN reflects the correct content

The goal is not fewer dashboard alerts. The goal is a working configuration that serves fresh content to users and bots while still protecting the origin.

Turn the note into a sprint

Cloudflare WAF / bot / 403 / 1020 access fixes

If this matches the live symptom, send the URL, what changed, and the affected pages so the first pass can stay bounded.