Menu

1 / 2

cf-cache-status DYNAMIC: Why Cloudflare Isn't Caching Your HTML (and How to Fix It)

DEV Community: webdev·Kausar Raza·5 days ago
#KkQwq9lU
#devtowebdev#devto#dev#cache#cloudflare
Reading 0:00
15s threshold

If you run curl -I against a site behind Cloudflare and see cf-cache-status: DYNAMIC , Cloudflare isn't caching that response at all. It didn't try and fail. It never considered it. Every request for that page goes through to your server, so you get Cloudflare's network and its DNS, but none of the caching.

That's how HTML works on Cloudflare by default, and it confused me for longer than I'd like to admit. My images, CSS and JavaScript were all coming back HIT , so I assumed the pages were cached too. They weren't. It only changed on 17 October 2026, when I added a cache rule to this site. You can still see the old behaviour today on the one path that rule leaves out, which makes it a handy live example.

Below are the headers from this site, what each cf-cache-status value actually means, why DYNAMIC and BYPASS are not the same problem, and the rule I use to cache HTML without caching anything I shouldn't.

Short answer: DYNAMIC means no cache setting applies to the response.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.