the docs say that `cf.cacheKey` is only
the docs say that
cf.cacheKey is only available for Enterprise accounts -- does that include accounts that have been granted Enterprise status via the Cloudflare for Startups program? I'm in the program and I cannot get cacheKey working for the life of me -- it seems to be always set to the request url5 Replies
or perhaps because I'm setting it in an Outbound Worker via Workers for Platforms?
I vaguely remember the
cf field not working in wfp for security reasonsCloudflare Docs
Limits · Cloudflare for Platforms docs
Cloudflare provides an unlimited number of scripts for Workers for Platforms customers.
hm that only mentions the limit being for user workers
yeah totally! I read that too, so I moved the
cf field to the outbound worker. and I see cf-cache-status come back as HIT with super fast latency. however, when I provide a custom cacheKey I notice that it always pulls from the same (wrong) resource
another symptom is that when I purge cache in my dashboard, it doesn't seem to take effect. I purge cache (by tag or everything), wait 1-2 minutes, and then when I make a fetch in my outbound worker with a cacheKey present, cf-cache-status still comes back as HIT