23 Replies
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
you don't happen to have a worker or anything overriding that, right? If you go to your account level in Cloudflare, there's a "Trace" option, "Begin Trace" and input
https://betaapp.slidesome.com, worth a sanity test, useful utility to learn tooUnknown User•7mo ago
Message Not Public
Sign In & Join Server To View
All rules have to live under rulesets
that's the default ruleset for all your cache rules
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
what was the cache rule you tried to create, just bypass cache?
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
would make more sense if it wasn't edge cache since you tried purging that before
you see cf-cache-status dynamic and still the old html?
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
you're using cache api in your function or something?
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
well where is Age coming from lol
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
oh sounds like asset preservation cache, was thinking it wouldn't be because index.html should still exist in both versions, but I guess in the new one it doesn't/it's all through functions?
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
sounds just like asset preservation cache to me
all the pages serving worker code is open source: https://github.com/cloudflare/workers-sdk/blob/52e9c71d21cd03d8d2fe5bea778ad9303ab3f0e7/packages/pages-shared/asset-server/handler.ts#L578C1-L578C48
GitHub
workers-sdk/packages/pages-shared/asset-server/handler.ts at 52e9c7...
⛅️ Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk
if you had an html page that existed before, it gets inserted into the asset preservation cache on every success
that asset preservation cache is checked before not found/fallback routing behavior
if there's nothing in code on your end, it's the only thing I can think of that would return an Age header, and the cache lives on your pages.dev but with the full url of your custom domain (as weird as that is), so it's both not clearable by you and specific to that url
(and of course the cache api is point of presence specific)
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
if it's in the asset preseveration cache, you simply don't
yea except I imagine when you "replaced" it, you didn't actually replace the index.html but instead got rid of it all together with ssr now handling it
if you had simply replaced the file, it would just serve the updated one
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View
or wait out the expiration/eviction of the cached asset (stop visiting the site, it'll be evicted after based on access frequency), or use a different subdomain
Unknown User•7mo ago
Message Not Public
Sign In & Join Server To View