what about token based file access? would that be a possibility?
what about token based file access? would that be a possibility?
HIt don't see why not, though again, you would have to build it yourself, or find a project that does it for you
CWhat do you mean "raise with Planetscale"? Don't see how they could help you with that lol
You need to make multiple requests to planetscale per invocation/request for Smart Placement to help.
What is the "Direct Connect" option? I was trying to find it in their docs but couldn't find anything. If it's TCP Connect or not using fetch/the http interface, then Smart Placement doesn't work with that
You need to make multiple requests to planetscale per invocation/request for Smart Placement to help.
What is the "Direct Connect" option? I was trying to find it in their docs but couldn't find anything. If it's TCP Connect or not using fetch/the http interface, then Smart Placement doesn't work with that
UHow many subrequests are you doing per request? If its only 1 smart placement wouldnt help at all it would be the same speed no matter where the worker is just depends if the worker takes longer of if it takes the user longer to connect.
HFor the 2-3 DB Transactions, they would still travel over a single request though no? So there isn't any response to the Worker until they all complete anyway
EWhat's the best place to ask Custom Domain support for Pages
C#pages-help
Kworking on workers api and now stuck on how to get all zones where do worker appear, i can`t iterate all zones and do not have all zones recorded in my app. is there any api route to collect all current routes attached to my worker in every zone?
JIf you hit
/accounts/xxx/workers/services/xxx/environments/production/routes in the API, you should get the routes for a specific workerKthanks a lot, it does solve the problem
Mcan i ask what does including the request here do
Mso if you dont include it, you only cache by the url, but if you do include it what do you cache by
Murl and method ? surely not also headers right
Mits taken from here
MMlooks like in miniflare including the other parameter doesn't matter then?
https://github.com/cloudflare/workers-sdk/blob/f728503bd363b6421c35346c30d2d3e77025d49f/packages/miniflare/src/workers/cache/cache.worker.ts#L40
so im wondering if it even makes a difference at all or why its included this way in the example
https://github.com/cloudflare/workers-sdk/blob/f728503bd363b6421c35346c30d2d3e77025d49f/packages/miniflare/src/workers/cache/cache.worker.ts#L40
so im wondering if it even makes a difference at all or why its included this way in the example
CGoing to be honest, not sure if it does anything different and might just be a bad example.
Mok, thanks
Mwhat does
cf-cache-status: hit header mean in workers, i thought you had to handle caching on your own using the cache runtime api?Mi still get the log for the worker invocation if i enable realtime logs but the cf-cache-status header is "hit" so i dont really get it
CYou do. If you're fetching an origin behind CF you might be getting the cache status from the origin you're fetching
CWorkers will always be invocated, they run in front of cache
Minteresting
Mim not fetching anything though 
UWhats your code then? Either doing a fetch or adding the cf-cache-status header yourself is the only ways you'd get a cache status header returned from a worker
Mhttps://github.com/mastondzn/cdn/blob/main/src/routes/images.ts this is everything that happens on this route note the header is x-cache-status not cf-cache-status
GitHub
Personal image/file uploader, built with Cloudflare Workers & R2. To be used mainly with ShareX. - mastondzn/cdn
Mthis is a worker route
Myou can see the header right
UThat code is adding the header x-cache-status.
M
Myeah i see that which is intended
Mbut the cf-cache-status also appears
Mwhich is what i find odd
UIt might be automatically added by the cache api since you are using that 
EIf you return a response directly from the cache api then its going to give
cf-cache-status: HITohh okay that makes sense
EBut if theres nothing in there then youre not going to get a MISS because Workers doesn't know what you intended, so it will just have no header
EAdding your own header is smart if you want to be sure whats happening, then you can add your own extra states as well if you find a need to
ESince you cant modify
cf- headersMokay thanks that makes sense actually
Mand also i wanna say i was using wrangler before v3 and now this is way better dx with the local dev mode great work guys 
Cminor but you can return your own cf-cache-status header from a worker, probably not a good idea, but I mean if you wanted to, could fake a miss
EFun, okay then
UYeah workers can add cf-<anything> just the rules stuff cant. or at the very least a few of the cf-<things> I tried worked
Ccan't override cf-ray but lots of other things you can fake
Mthis cache api is actually nice you can upload stuff and instantly insert in your cache aswell so even the first request can be cached, very cool
