Cache-Control: public, max-age=0, must-revalidate.




not_found_handling = "single-page-application" doesn't seem to quite work without handling in the worker? Am i right about that? You want to bind it and hand the request back to assets to get the correct asset.Also, On a pro account when using the Cache API in a worker, it’s cached in the nearest colo to where the worker is executed from, from what I understand.That's the same for any plan. It's not "the nearest colo to the worker", workers run directly in colos. Cache is all PoP based now though
My question is there any way to cache in a location closer to using that api on the pro plan?no, cache api is only local. What do you mean "closer"? though, closer to what? Maybe you want something like Smart Placement to run the worker closer to your backend?
_headers files to modify static file request headers is not currently supported, right?Cache Rules does not seem to work either,cache-control: public, max-age=0, must-revalidatecf-cache-status headerscross-origin-embedder-policy: require-corp
Transform Rules, the same effect as with Pages can be achieved.
