you could have a transform rule modify request header and include it:

ChaikaOP•1/28/24, 11:03 PM

(assuming this is a simple fetch worker, might get more complex if you're using service bindings. For Queue customer/cron/etc iirc its just always your workers.dev)

CChaika you could have a transform rule modify request header and include it:

dave•1/28/24, 11:50 PM

Hmm I wanted something that would work on any zone without configuration needed.

tayek•1/29/24, 1:25 AM

Are workers suitable for high throughput websocket connection that lives for 1-5 minutes? Or is it too expensive?

John•1/29/24, 2:17 AM

Using cloudflare pages and deploying a nuxt website that uses cloudflare workers. I'm getting this error:

John•1/29/24, 2:17 AM

John•1/29/24, 2:18 AM

doesn't seem to be an issue with my code as it works fine in development

John•1/29/24, 2:20 AM

some rust function seems to be failing, but my app doesn't use rust

John•1/29/24, 2:20 AM

very weird error

JJohn Using cloudflare pages and deploying a nuxt website that uses cloudflare workers...

Isaac McFadyen•1/29/24, 2:22 AM

Nitro (Nuxt's build/server system) uses Rust, I believe.

Isaac McFadyen•1/29/24, 2:22 AM

So probably a problem with whatever Nitro is doing in the build.

John•1/29/24, 2:23 AM

Potentially

John•1/29/24, 2:23 AM

Rollup also uses rust

John•1/29/24, 2:23 AM

I found this in source code for rollup

John•1/29/24, 2:23 AM

John•1/29/24, 2:23 AM

seems to be the error

John•1/29/24, 2:23 AM

but I have absolutely no idea how to mitigate it from my source code

John•1/29/24, 2:25 AM

~~this honestly is starting to look like a developer's worst nightmare~~

IIsaac McFadyen So probably a problem with whatever Nitro is doing in the build.

John•1/29/24, 2:30 AM

I think the issue might be specific to cloudflare. When I run

npx nuxt build

npx nuxt build

on my machine, it works.

John•1/29/24, 2:34 AM

Nevermind

John•1/29/24, 2:34 AM

npx nuxi build --preset=cloudflare_pages

npx nuxi build --preset=cloudflare_pages

fails on my machine

John•1/29/24, 2:37 AM

found the issue - it was in one of my libraries

vakno•1/29/24, 8:39 AM

How many routes are limited for workers? I have a webshop where i need to change SEO of a lot of urls 1000+
Is

*.domainname/*

*.domainname/*

considered one route? Or will each url targetted be one route?
Sorry this might be a stupid question.

kian•1/29/24, 9:15 AM

1,000 routes per zone, and

*.domainname/*

*.domainname/*

is a single route.

kian•1/29/24, 9:15 AM

Kkian 1,000 routes per zone, and `*.domainname/*` is a single route.

vakno•1/29/24, 9:31 AM

Thank you! How much can workers that are run on whole domain decrease page speed ( the workers are pretty simple, like changing H1 to H3?
Can i avoid sending requests to static files?

Vvakno Thank you! How much can workers that are run on whole domain decrease page speed...

dave•1/29/24, 3:10 PM

if you have static files, I recommend using Cloudflare Pages + Workers, if you don't want to pay for a Worker on the static file requests.

https://www.ai.moda/en/blog/do-not-use-custom-domains-for-workers <- this is how my team sets up Workers to play nice with Pages for static files

you can see how it looks in action at https://auth.ai.moda/pages/v1.0.0/login

^ we don't pay for any of the requests except for ones to

/api/v0.0.1/*

/api/v0.0.1/*

ai.moda

Don't use custom domains for Cloudflare Workers (but do)

Workers costs money, Pages are free on every request. You can't use a

SSO - ai.moda

SSO for ai.moda.

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

I recommend versioning your Workers' routes for things you will have to maintain compatibility with long-term. That way if you want to refactor/rewrite your Worker in the future, you don't have to be scared about breaking things in production for existing users on the older Workers.

Isaac McFadyen•1/29/24, 5:24 PM

I'd also just add that Workers on the whole domain actually increase the startup time of the Worker because of this optimization: https://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers

kian•1/29/24, 5:47 PM

Cloudflare does, since they control the end which is the Worker

kian•1/29/24, 5:47 PM

If you mean you're encrypting stuff yourself, i.e PGP, then theoretically anything your Worker can do then Cloudflare could do.

Isaac McFadyen•1/29/24, 5:55 PM

If you're using your own keys and doing your own encryption then yeah, CF can't see that data.

Isaac McFadyen•1/29/24, 5:55 PM

But Cloudflare could theoretically see your key. They don't. But it's possible, if someone were to pull the memory of an ongoing Worker (very difficult and I'm not even sure if it's possible)

Isaac McFadyen•1/29/24, 5:56 PM

They'd need to pull the memory of the worker, parse it somehow and extract the key, and then also have access to all the traffic that the Worker accepts (which is encrypted with TLS with Cloudflare's own keys) in order to decrypt it

IIsaac McFadyen I'd also just add that Workers on the whole domain actually increase the startup...

dave•1/29/24, 9:00 PM

the way i'm doing it with a subpath is fine though, right?