A cache somewhere cannot be cleared, causing pages.dev to give different results based on hostname
I have Cloudflare Pages set up for a domain that I own. I put up a test file and then I removed it and redeployed. The page is still there and cannot be removed.
I cleared the Cloudflare DNS proxying cache, turned on development mode, and turned off Always Online, and that didn't help. I deleted the Pages build cache and redeployed, and it's still there. I deleted my Cloudflare Pages project and recreated it, and that didn't fix it. I turned off Cloudflare DNS proxying to use a regular CNAME record, and it's still there.
When I access the Pages URL (https://t-rex-army.pages.dev/test), it's gone. When I access the URL on my site (https://t.rex.army/test), it's still there. That means that pages.dev itself is delivering different versions based on the hostname. How can this be fixed?
2 Replies
Do you see a CF-Cache-Status header in the response?
Or does it say that the file is being cached in your browser?
cf-cache-status: HIT for the bad version.
I've tried clearing the browser cache and using different browsers.
What's strange is that the other pages don't have that response header.
No cf-cache-status.