Cache API working on workers.dev but not custom domain
Original message was deleted
CSend
https://cache-bug.spead.dev/ through trace, what cache rules/page rules do you hit?CPages Functions are special and its cache api usage always lives on the pages.dev and not your custom domain
Caw, was hoping for something easy. Do you have any page rules/cache rules which disable caching on that zone?
Cfwiw this is not reproducible https://new-test-boop.chaika.win/
Coh, are you using Worker Routes or Custom Domains?
Cwhat happens if you change the s-maxage=86400 instead of 6000?
Csilly question but on your overview, do you have Dev mode on?
Cyea the overview tab, or under Caching -> Configuration
Cthere's a few rollouts going on rn
Cif both are free zones, probably what connects them
Cwould think I would be able to repro it then tho, unless there's some other common configuration you do to both sites
Cyou showed the rules overview tab but not the pages rules tab
CI tested on a domain with wildcard dns
Cthe redirect rule could maybeeee, you could try disabling for 10 seconds and testing
Cwhen you use a fake domain name, it should be processed through your zone's rules with that fake domain name/url/etc iirc
Coh lol, something dumb, whoops
CI know that it's a documented behavior that rules apply to caching api from workers, w/ the hostname
Cbut this isn't quite rules just applying lol
Cit's kind of weird and I'm not sure fully documented anywhere
Cthe docs do warn against this tho lol
https://developers.cloudflare.com/workers/runtime-apis/cache/
https://developers.cloudflare.com/workers/runtime-apis/cache/
When using the cache API, avoid overriding the hostname in cache requests, as this can lead to unnecessary DNS lookups and cache inefficiencies. Always use the hostname that matches the domain associated with your Worker.
CI'll make an internal thread (or a docs github issue) asking for better docs there about the behavior of rules and such, it's only mentioned in a really old change log they even apply
