H
HHH
env.variable_name, right?HHH
I
A
DD
=response-cache-control query parameter on Backblaze B2. It works fine on R2 though. I'm using aws4fetch for signing.D=%3D on the signed URL worksD
CDDH
III
HCC
F
). The integration of Workers include Supabase Auth? If so, should I use it in my project to auth users, or I can just stick to the client-side from react? Also, is there anyone who tried and made this work who eventually has some repo as a reference? Thanks a lot in advance.
ZZZZ
A
V
KF
M
BZC
N
cf: {
cacheTtl: 3600,
cacheEverything: true,
}, in my fetch request.CSo i am expecting for the same request with in my window of an hr, the 2nd fetch response would be taken from the cache not go to make another http request correct ?Cache by default is per colo/cf dc, and some Cloudflare Points of Presence even have multiple colos, so you might be routed to a different one/different visitors will certainly be, and get MISS's, plus TTL is just a max and CF may evict it far before then based on access frequency.
if this is the case why for every fetch request i do the worker gets called and returns the response?The worker will always be invocation/run on every request, even if using cache
How can i validate that this is from the cache or not?Check response headers for CF-Cache-Status
III
RR
env.variable_nameresponse-cache-control%3Dcf: {
cacheTtl: 3600,
cacheEverything: true,
},function myNewFunction(env) {
// use env here
}
export default {
async fetch(req, env) {
myNewFunction(env);
// Do more stuff
}
}
CDCloudflare Developers / pages-helpCDCloudflare Developers / workers-and-pages-helpCDCloudflare Developers / workers-and-pages-help