Dom
CDCloudflare Developers
•Created by Dom on 2/19/2025 in #pages-help
Previously deployed index.html still gets served
On a 'fun' note - while for me the issue seemed to be resolved now, The other day a ghost index.html appeared again after things were working for days.
I published and then deleted anoter redirecting index.html and for now, it's resolved.
15 replies
CDCloudflare Developers
•Created by Dom on 2/19/2025 in #pages-help
Previously deployed index.html still gets served
It wasn't for me.
I had the same problem across multiple browsers, incognito windows and devices. It was definitely CF serving the file.
As @sergey said - it's probably asset retention related.
Would be good to get a way to tell CF to wipe all retained assets.
I even thought about killing Page and setting up a new one on the same url but I didn't wana risk further problems.
15 replies
CDCloudflare Developers
•Created by Dom on 2/19/2025 in #pages-help
Previously deployed index.html still gets served
Yea, but I how do I tell it to forget about it?
Clearing the cache doesn't do anything
15 replies
CDCloudflare Developers
•Created by Dom on 2/19/2025 in #pages-help
Previously deployed index.html still gets served
just found this:
https://community.cloudflare.com/t/custom-domain-not-reflecting-updated-cf-pages-app/618259
15 replies
CDCloudflare Developers
•Created by Dom on 2/19/2025 in #pages-help
Previously deployed index.html still gets served
I temporarily solved it by adding a /start route and then publishing a index.html that does a html redirecto to /start.
ten I removed the index.html again.
Now I sstill get the index.html with the redirect served, even though its no longer present in the deployment
15 replies
CDCloudflare Developers
•Created by Dom on 2/18/2025 in #workflows-beta
Hey!
Originally, my binding was called
IMPORT_WORKFLOW
but that gave the same error, so I thought I call it USER_WORKFLOW
bu still no luck3 replies
CDCloudflare Developers
•Created by Dom on 2/18/2025 in #workflows-beta
Hey!
wrangler config:
vite config:
3 replies