Deleted page is still accessible
There's a page that's been deleted for months. A user notified me that the page is still accessible. I've gone and deleted all the same preview-based deployments in Cloudflare Pages, but the URI is still accessible. This only happens for one of my preview URLs (which has a dedicated subdomain) not my production, main site.
I realize from my research that some cached results are expected but based on my reading that should only be for a week or a month maybe. Not half a year.
What do I need to do to ensure that when I publish new versions of my Docusaurus site that old URLs are no longer accessible when I delete a page?
24 Replies
It sounds like that preview must have the file.
Yeah there is the preservation cache which lasts a week max, after that, unless the file is uploaded in the ver, it. can't be accessed
Unfortunately I don't think I am able to fix or diagnose this on my own. I need to get rid of the data, but I don't know how.
What do you recommend?
what's the url?
https://next.recyclarr.dev/wiki/sqp-configs/#sqp-3
Here is the removal commit: https://github.com/recyclarr/wiki/commit/07381d047d46c21d6fbe7a2ad37175b307359382
Clearly I lost track of time.. this happened on June 3rd this year, definitely not 6 months! Sorry 😂
However it sounds like it's been long enough that this should definitely be gone!
It does 404 for me, can you go to /cdn-cgi/trace and see what colo you're hitting?
also make sure it's not browser cache
I don't know what that is, how do I get to that?
remove the ip field
yeah i get a 404 on the same server
I tried this on two different physical machines
and I did CTRL+F5
I don't see how it can be a cache on my side
Another user also saw it which is the whole reason I even know about it
if you open in incognito, does it 404?
Nope
If it helps I get a 200 response with (snipped unrelated headers)
HTTP/3 200 content-type: text/html; charset=utf-8 vary: accept-encoding cf-cache-status: DYNAMIC access-control-allow-origin: * age: 79561 server: cloudflare x-content-type-options: nosniff cf-ray: 974b66d21e535008-IADThat age is interesting, should be cached for less then 22 hours then/removed much more recently
interesting..
That's a cache age set on the CDN side?
how do i still get a 404 on that same server :lul:
My guess tells me it's a regional thing; there's probably 1 server that didn't clean this up
ok i got a 200 without the fragment
though the fragment isn't sent server side so no idea how that'd cause a different cache key
I thought the age header would only ever exist on a page served from the asset retention cache, so should mean this update is on its way out, just later then expected 🤔
yeah, i can confirm it's in cache but no idea why it's still in cache
it's a little complicated but expected in the current config
?link @voidpointer can you link your account please
Please use the /link command to authenticate with your Cloudflare account and link it to your Discord user. This helps Cloudflare employees access your details more quickly and provide support. It also makes future support requests easier, since your account will already be linked.
Ok it says linked successfully
Escalated to the support team, they should make a ticket for you and escalate to eng.
I appreciate all of you very much!
Hey folks, I haven't gotten an email yet or anything regarding a support ticket. Is this something I'm supposed to be notified via email about?