That code is fetching from another domain - if that domain takes a while to respond, your worker will take the same time

The worker itself will already be very fast

is there any other way to fetch the another domain with faster response?

You could try caching the responses from that domain

But other than that, the only thing to do is to get the other domain to be faster

how?

you can store json files in R2 super easily

@ me or msg me if you need code for it I have a nearly identical worker which generates and saves text files 20+ times per minute in bursts without issue

hi, I need to save data for maximum 5 minutes - cache because I am making discord bot and /setup command has more stages - buttons, select menus, modals and I have to save somewhere things that user entered, I was thinking about Cache, but it is not right (at least I think so)

something like redis would be great

Durable Objects would probably work fine

question (please ping when replying): regarding smart placement beta, does the algorithm automatically separate between different URI path routes when deciding whether to place the worker edge server closer to the site's API server or to the actual user? I'll give 2 examples: #1 - I have a route on my worker that calls 3-4 requests from my API/DB server #2 - I have another route which just does a single request from my API/DB server Would it apply the placement globally for the worker or just for each URI path? I assume there's no real harm for #2 of placing it anywhere along the path since it's 1 request from both ends but I figured i'd ask anyway im honestly just curious

Not currently, no

It's done on a per-Worker basis

ah right, different path would usually be a different worker

I'm mainly asking for the purpose of stuff like pages functions, not actually sure how those are loaded up.

They're all a single Worker

right. so I think my question remains, if a different function is doing more requests than the other, how would that be handled?

All functions are combined into a single worker

Then that'd be what placement prioritises

My custom domains are shown as inactive in the cloudflare dashboard, even though they work. Does someone else have the same issue?

You are talking about Worker Custom Domains, I assume? Specifically, the certificates column showing inactive? If you've deleted the certificate (and don't need it, or made another Adv. one to replace it), it's expected. You don't need the certificates if the custom domain is already covered by your Universal SSL Cert (which covers first level subdomains, i.e *.yourwebsite.com). If you're not talking about that, please specify the exact product/menu you're talking about

Thanks for the response. Right, the certificate of the top level domain is shown as inactive.

If you don't need it (already covered by your universal ssl), or manually deleted it, that's fine

It's not saying the Custom Domain itself is inactive, it's just saying the Adv. Cert it issued for it is not active/was deleted

Thank you, just checked the edge certificates, and the "advanced" certificate is indeed shown as "Active" there but shadowed by the universal

On another note,

wrangler publish

started grepping text files inside

build/

and uploading them as modules.

Uploading additional modules:
- sitemap.txt (text)

How can i stop this new behaviour?

that's weird, it should still show as Active in the Custom Domains tab then as far as I know. It doesn't really matter too much though as long as it is renewing or not needed

Adding the line to wrangler.toml fixed this

toml
rules = [{ type = "Text", globs = [], fallthrough = false }]