You’re not doing any I/O so Date.now() will never increment
You’re not doing any I/O so Date.now() will never increment
KUse methods like setTimeout or scheduler.wait
UI see, thanks for the reference
Uvery helpful
Ui was trying to do it without awaits to test guarantees on DO gates 
Umaybe settimeout will work..
KYou can put a GUID in the global scope but that’s about it.
Nope.
Nope.
LHello, is there an endpoint available to add or update environment variables for workers? I have found this endpoint, but I'm unsure about its usage. It would be greatly appreciated if an example could be provided.
LAnd I found that the "type" parameter in the request body for updating Environment Variables in the Cloudflare dashboard is not supported in the endpoint.
LInteract with Cloudflare's products and services via the Cloudflare API
DIs there any benefit or perf difference between these two?
DWe've always be going for the former, since it allows us to add Cloudflare Pages easily to the same domain later if needed with zero downtime.
Dwait wait wait what, fetches work in the same zone?!
Dwithout service bindings?
Dis this new?
Dif I use custom domains, can a Worker do a fetch to itself?
Dwoah
UOnly the custom domains support the "no cold start" afaik that does the script loading during tls
Udoubt it makes that much of a difference tho tbf
Ciirc that's still broken above a certain compat date or without a special flag
CGitHub
Which Cloudflare product(s) does this pertain to? Workers/Other What version of Wrangler are you using? 2.9.0 What operating system are you using? Mac Describe the Bug Same zone worker <-> wo...
Uservice bindings are better anyways 
KI have a worker which acts as a proxy to a third-party upstream service. The upstream service needs the IP of the original requester. The upstream service only accepts IPv4 sadly what we just found out. Is there a way to disable IPv6 for the worker to always get the IPv4 IP address?
CUse a Custom Domain/Route on your own domain, disable IPv6 on the domain/zone
CWorker are behind proxy so that'll just work. You can disable IPv6 via API even on free plan
The limitation is just passing an IPv6 address at all, right? Workers won't force IPv6 if the service doesn't have any AAAA records (because how could it?), unless the upstream service runs on Cloudflare in which case it'd get the Workers Cross-Cloudflare IPv6 IP.
Should really pester them to at least support IPv6 Addresses in 2024 lol
The limitation is just passing an IPv6 address at all, right? Workers won't force IPv6 if the service doesn't have any AAAA records (because how could it?), unless the upstream service runs on Cloudflare in which case it'd get the Workers Cross-Cloudflare IPv6 IP.
Should really pester them to at least support IPv6 Addresses in 2024 lol
Dwhy would
/path/* be different than /* for cold starts?Dahh, so
/* and custom domains are the same then?DI'm confused, no other difference though, right?
I^ Custom domains issue a certificate for the entire (sub-)domain (that's one of their downsides actually, they don't use the existing wildcard cert they issue their own cert)
Disn't that a positive?
Udepends if you consider that a downside I guess 
ISo if you ever have a Worker that you don't want to be easily discovered via cert transparency logs, don't use Custom Domains
II mean... I don't really think it's a positive? There's not much benefit to re-issuing a cert.
IIf you have one for
*.example.com why issue one for foo.example.com?Dsanity check, are these messages talking about the same feature? https://discord.com/channels/595317990191398933/779390076219686943/1196903837257170974 and https://discord.com/channels/595317990191398933/779390076219686943/1196837523729682586
KDisabling IPV6 is still an option while its disabled in the UI? Nice to know
Doh, so the certificate handling is different, but the TLS/cert perf is the same?
KYes its the limitation that the upstream service needs an IPV4 because it still does not support IPV6
KAnd it needs to be a valid IPv4 because otherwise there will be connection issues between the client and the service
Cvia the api yea
CYou can always delete it
Cit's just an adv. cert under Edge Certs
Cif you're fast enough or script it, you can delete it before it issues
Dso when I do curl -v, I see only the SSL cert for the domain and not the wildcard ;P
Cyea Worker Custom Domains are just really hacky. You don't need ACM to delete them, or use it. They do count against your ACM Quota though, and show up there
USpeaking of ACM I think the workers custom domains does use your limit of ACM if you have it or it least did in the past
Kthe main feature of custom domains (imo) is not having same-zone fetch issues, but that has been broken since day 1
K
UI just like how it shows in the dns thats why I use it
