Cloudflare Developers•2y ago

Use methods like setTimeout or scheduler.wait

kianOP•1/16/24, 8:36 AM

https://developers.cloudflare.com/workers/reference/security-model/#step-1-disallow-timers-and-multi-threading

usmannk•1/16/24, 8:40 AM

I see, thanks for the reference

usmannk•1/16/24, 8:40 AM

very helpful

usmannk•1/16/24, 8:41 AM

i was trying to do it without awaits to test guarantees on DO gates

Kkian Use methods like setTimeout or scheduler.wait

usmannk•1/16/24, 8:43 AM

maybe settimeout will work..

kianOP•1/16/24, 8:48 AM

You can put a GUID in the global scope but that’s about it.

Nope.

Leo_C•1/16/24, 9:27 AM

Hello, 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. MeowHeartCloudflare

Leo_C•1/16/24, 12:50 PM

And I found that the "type" parameter in the request body for updating Environment Variables in the Cloudflare dashboard is not supported in the endpoint.

Leo_C•1/16/24, 12:50 PM

https://developers.cloudflare.com/api/operations/worker-script-environment-patch-settings

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

dave•1/16/24, 3:13 PM

Is there any benefit or perf difference between these two?

routes = [
  { pattern = "https://hello.example.com/*", zone_name = "example.com" }
]

routes = [
  { pattern = "https://hello.example.com/*", zone_name = "example.com" }
]

routes = [
  { pattern = "hello.example.com", custom_domain = true }
]

routes = [
  { pattern = "hello.example.com", custom_domain = true }
]

dave•1/16/24, 3:17 PM

We'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.

Original message was deleted

dave•1/16/24, 3:18 PM

wait wait wait what, fetches work in the same zone?!

dave•1/16/24, 3:18 PM

without service bindings?

dave•1/16/24, 3:19 PM

is this new?

Original message was deleted

dave•1/16/24, 3:20 PM

if I use custom domains, can a Worker do a fetch to itself?

dave•1/16/24, 3:20 PM

woah

Ddave Is there any benefit or perf difference between these two? ```toml routes = [ ...

Unsmart•1/16/24, 3:24 PM

Only the custom domains support the "no cold start" afaik that does the script loading during tls

Unsmart•1/16/24, 3:24 PM

doubt it makes that much of a difference tho tbf

Original message was deleted

Chaika•1/16/24, 3:39 PM

iirc that's still broken above a certain compat date or without a special flag

Chaika•1/16/24, 3:39 PM

https://github.com/cloudflare/workerd/issues/787#issuecomment-1597396873

GitHub

🐛 BUG: Worker <-> Worker request over `custom_domain` returns insta...

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...

Unsmart•1/16/24, 3:40 PM

service bindings are better anyways

kev-ac•1/16/24, 3:55 PM

I 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?

Kkev-ac I have a worker which acts as a proxy to a third-party upstream service. The ups...

Chaika•1/16/24, 5:38 PM

Use a Custom Domain/Route on your own domain, disable IPv6 on the domain/zone

Chaika•1/16/24, 5:40 PM

Worker 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

Original message was deleted

dave•1/16/24, 7:47 PM

why would /path/*/path/* be different than /*/* for cold starts?

dave•1/16/24, 7:48 PM

ahh, so /*/* and custom domains are the same then?

Original message was deleted

dave•1/16/24, 7:50 PM

I'm confused, no other difference though, right?

Isaac McFadyen•1/16/24, 8:00 PM

^ 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)

IIsaac McFadyen ^ Custom domains issue a certificate for the entire (sub-)domain (that's one of ...

dave•1/16/24, 8:01 PM

isn't that a positive?

Unsmart•1/16/24, 8:01 PM

depends if you consider that a downside I guess LUL

Isaac McFadyen•1/16/24, 8:01 PM

So if you ever have a Worker that you don't want to be easily discovered via cert transparency logs, don't use Custom Domains

Isaac McFadyen•1/16/24, 8:01 PM

I mean... I don't really think it's a positive? There's not much benefit to re-issuing a cert.

Isaac McFadyen•1/16/24, 8:01 PM

If you have one for *.example.com*.example.com why issue one for foo.example.comfoo.example.com?

Original message was deleted

dave•1/16/24, 8:01 PM

sanity check, are these messages talking about the same feature? https://discord.com/channels/595317990191398933/779390076219686943/1196903837257170974 and https://discord.com/channels/595317990191398933/779390076219686943/1196837523729682586

CChaika Worker are behind proxy so that'll just work. You can disable IPv6 via API even ...

kev-ac•1/16/24, 8:02 PM

Disabling IPV6 is still an option while its disabled in the UI? Nice to know

Original message was deleted

dave•1/16/24, 8:02 PM

oh, so the certificate handling is different, but the TLS/cert perf is the same?

CChaika Worker are behind proxy so that'll just work. You can disable IPv6 via API even ...

kev-ac•1/16/24, 8:02 PM

Yes its the limitation that the upstream service needs an IPV4 because it still does not support IPV6

kev-ac•1/16/24, 8:03 PM

And it needs to be a valid IPv4 because otherwise there will be connection issues between the client and the service

Kkev-ac Disabling IPV6 is still an option while its disabled in the UI? Nice to know 😅

Chaika•1/16/24, 8:04 PM

via the api yea

Chaika•1/16/24, 8:04 PM

You can always delete it

Chaika•1/16/24, 8:04 PM

it's just an adv. cert under Edge Certs

Chaika•1/16/24, 8:04 PM

if you're fast enough or script it, you can delete it before it issues

IIsaac McFadyen If you have one for `*.example.com` why issue one for `foo.example.com`?

dave•1/16/24, 8:04 PM

so when I do curl -v, I see only the SSL cert for the domain and not the wildcard ;P

Original message was deleted

Chaika•1/16/24, 8:05 PM

yea 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

Unsmart•1/16/24, 8:05 PM

Speaking 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 LUL

kianOP•1/16/24, 8:05 PM

the main feature of custom domains (imo) is not having same-zone fetch issues, but that has been broken since day 1

kianOP•1/16/24, 8:05 PM

Unsmart•1/16/24, 8:06 PM

I just like how it shows in the dns thats why I use it

Unsmart•1/16/24, 8:06 PM

service bindings are better for fetching anyways so that feature is useless imo

Use methods like setTimeout or scheduler.wait

Similar Threads

Similar Threads

Similar Threads