you have to manually enable it and then it works
you have to manually enable it and then it works
Lbut i don't understand why it works like that
HI don't actually think that setting is covered by the Terraform provider
Lin any case, the
<account>.workers.dev is an actual zoneLi think it's the only way you can trigger your functions unless you register your own domain
HIt is a real zone, but afaik you can't actually add it as a route, you need to do
workers_dev = true in your wrangler.toml
Lyeah, you cannot add it as a route
Lif i try to add a route, i see i have no zones available
Lso i'm not sure what that is actually
HIt's a special
HIt's a Zone, but not your zone
HSo you can't actually control it
Lso you cannot have routes, unless you add a custom domain to your worker
HOr use
wrangler
DHey all, I need to get my API request latency down dramatically globally. I am using:
Workers, TS, Hono, Upstash Redis, and Turso
Workers, TS, Hono, Upstash Redis, and Turso
DI would like to get it from 150-300 -> around 80
DTheres an API that does this, could it be that they just cache every response to cf cache? They deploy to workers and use hono
ULatency there is going to be highly dependent on where your databases are
DIs turso good for this? Would D1 be better?
DCF-Cache works great, but I need to bill the user for every request. Any way to do this?
JIs it possible to use got (https://www.npmjs.com/package/got) in a worker? I'm trying but getting a bunch of errors about failed imports and such.
JMy main issue at the moment is sometimes I am doing some subrequests with the built in
fetch
Cno, looks like that uses node:net/raw sockets
CWorkers use V8 Isolates, in a web like environment. Not node,js, although they support some node functions via node compat. They support TCP Sockets through their own interface, but not node networking or raw sockets, nor UDP
CYour options are pretty much:
Use Fetch which sort of goes out through the CDN/normal request path
Use something built on top of custom TCP Sockets API which uses Cloudflare WARP IPs (no list of them). You'd suffer from not being able to keep connections warm/new connection each time and such though
Use Fetch which sort of goes out through the CDN/normal request path
Use something built on top of custom TCP Sockets API which uses Cloudflare WARP IPs (no list of them). You'd suffer from not being able to keep connections warm/new connection each time and such though
C521 is web server down
Error 521 occurs when the origin web server refuses connections from Cloudflare. Security solutions at your origin may block legitimate connections from certain Cloudflare IP addressesIf it's something you control, does it work through a normal proxied record? Are you specifying a non-standard port?
LHi everyone
I've been having problems using Workers & Pages and D1
With my team we created a D1 database and we want to "connect " it with our web app. We want to connect Backend with Frontend, pulling data from the D1 database and use it on our app (i don't know how to call it)
Could someone help?
I've been having problems using Workers & Pages and D1
With my team we created a D1 database and we want to "connect " it with our web app. We want to connect Backend with Frontend, pulling data from the D1 database and use it on our app (i don't know how to call it)
Could someone help?
Bhelp with what
LI have some data in the format on JSONs which i would like to insert in my remote D1 database, which im not being able of doing, and later make querys
Lso i would need help on how to insert this data into the DB
KDoes anyone know if there is a worker that will allow me to browse my R2 backup folder of JPGs ? And ideally convert them to thumbnails on the fly & save a copy in a /thumbnails folder too. (I don't want to use the $5pm Images product). I'm happy to write one myself, but I am currently time poor.
OCan I set cache headers from worker and have the next requests for the same URL skip the worker completely?
RI'm finding "Purge Everything" is failing to purge cache entries written using the Cache API and I've got a suspicion it's related to the fact we open our own cache rather than use the default, i.e.
Can anybody confirm this is expected behaviour and if so, is there a way to purge the 'app' cache instead of the default one?
caches.open('app') vs caches.default.Can anybody confirm this is expected behaviour and if so, is there a way to purge the 'app' cache instead of the default one?
HYou cannot, no. All requests to a Worker route result in an invocation
OA bit tangential but related: how does one protect against major cloud bill if DDOS happens with workers?
RDoes this mean there's no way to purge a custom cache across all data centers?
RI can't really find any real documentation on
caches.open , I wonder what the use cases for it are?R(tbh we used it because we were using Shopify Hydrogen as a reference 
)
)
HMDN Web Docs
The open() method of the
CacheStorage interface returns a Promise that resolves to
the Cache object matching the cacheName.
CacheStorage interface returns a Promise that resolves to
the Cache object matching the cacheName.
HThough
caches.default isn't actually a thing there...Ryeah I saw that, but it doesn't really help with the practical differences regarding CF's cache impl. + purging
RMight be worth updating the docs here https://developers.cloudflare.com/workers/reference/how-the-cache-works/#purge-assets-stored-with-the-cache-api to mention some of that applies to
cache.openCloudflare Docs
How Workers interacts with the Cloudflare cache.
HIf it makes a difference, the Cache API doesn't validate that the domains of the URLs you pass in exist. So you could just make up a fake domain to create different cache spaces
Rha interesting. It's a really funny API to work with tbh. Kinda dancing around http even though a lot of use cases would be simpler by just passing a string as the cache key.
Rout of interest, are cache entries written via the Cache API considered part of the zone the worker is running on or is it the zone of the url being cached?
Re.g.. worker on foo.com caches something under bar.com
HThe zone of the Worker. You can cache a
cloudflare.com request, but it won't affect the actual cache for cloudflare.comHWould be very bad if you could mess with other people's caches that way...
RYeah that's what I was thinking, although this flow chart had me worried https://developers.cloudflare.com/workers/reference/how-the-cache-works/#single-file-purge--assets-cached-by-a-worker
Cloudflare Docs
How Workers interacts with the Cloudflare cache.
R(we're caching API calls to shopify which I know is also on CF)
Rbut I guess that's actually specific to the ability to single-file purge, i.e. because shopify is on CF then we can't single file purge, as they own that... but maybe we should just change it to be cached under
https://{uuid}.com or https://domain-we-own.com and then we can single file purge?