if you want to use workers, then you can just use routes

ChaikaOP•7/5/24, 6:04 PM

https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/

Cloudflare Docs

Workers as your fallback origin · Cloudflare for Platforms docs

Learn how to use a Worker as the fallback origin for your SaaS zone.

ChaikaOP•7/5/24, 6:05 PM

one wildcard to catch all, or specific ones for each custom hostname

CChaika if you want to use workers, then you can just use routes

johtso•7/5/24, 6:11 PM

hmm, so if I have domain foo.xyzfoo.xyz
created fallback origin fallback.foo.xyzfallback.foo.xyz pointing at the dummy IP
then made a CNAME proxy.foo.xyzproxy.foo.xyz pointing at fallback.foo.xyzfallback.foo.xyz
then set up CNAME from foo.otherdomain.examplefoo.otherdomain.example pointing at proxy.foo.xyzproxy.foo.xyz and added foo.otherdomain.examplefoo.otherdomain.example as a custom hostname

would the workers route then look something like foo.otherdomain.example.com/*foo.otherdomain.example.com/*? can I match on that external domain?

Jjohtso hmm, so if I have domain `foo.xyz` created fallback origin `fallback.foo.xyz` po...

ChaikaOP•7/5/24, 6:13 PM

then made a CNAME proxy.foo.xyz pointing at fallback.foo.xyz

That's unnecessary, they can just cname to fallback or any proxied record on your domain

johtso•7/5/24, 6:14 PM

"they" being me

ChaikaOP•7/5/24, 6:14 PM

rest of that makes sense yea. Having CF for SaaS on a zone enables you to make routes that don't match your zone/match externals

johtso•7/5/24, 6:15 PM

awesome

johtso•7/5/24, 6:16 PM

I'm not sure why the docs recommend having that intermediate CNAME proxy

johtso•7/5/24, 6:16 PM

there must a good reason

Jjohtso there must a good reason

ChaikaOP•7/5/24, 6:19 PM

oh, looks like they just wanted you to do *.customers.saasprovider.com*.customers.saasprovider.com, so people could cname like google.customers.saasprovider.com

johtso•7/5/24, 6:22 PM

hmm, what advantage would that have? that I could route based on that domain so they could change their own domain if they want and not break the routing?

Jjohtso hmm, what advantage would that have? that I could route based on that domain so ...

ChaikaOP•7/5/24, 6:24 PM

that I could route based on that domain so they could change their own domain if they want and not break the routing

No, how would CF know what CNAME each request used if they're using ext dns? The only thing they get is the host header and the ip requested

ChaikaOP•7/5/24, 6:25 PM

I think advantage is just more pretty

provides a friendly and more flexible place for customers to route their traffic.

and you could always point them to some other unproxied origin them if needed I guess for a specific customer

CChaika > that I could route based on that domain so they could change their own domain...

johtso•7/5/24, 6:26 PM

that makes sense, my dns understanding is a bit thin. so then what's the advantage of them CNAMEing google.customer.saasprovider.com instead of just everyone CNAMEing customer.saasprovider.com?

johtso•7/5/24, 6:26 PM

ah that makes sense

johtso•7/5/24, 6:27 PM

aesthetics and then flexibility of switching up the routing for just that customer outside of the SaaS functionality

johtso•7/5/24, 6:28 PM

well, I'm hitting my hello world worker through my custom domain with SSL, thanks for the help

Jjohtso aesthetics and then flexibility of switching up the routing for just that custom...

valkyrie_pilot•7/6/24, 2:06 AM

you could also do some shard scaling by pointing them at different IPs so that every node doesn’t know how to route every single request

[

[ ⚡ ] ElBretxa•7/6/24, 8:06 PM

Hey, my team and I have a website for a project, but when trying to go in the website, we get an error saying

Error: Connection closed.
    at t (23-63969a852fd53b0b.js:2:17735)

Error: Connection closed.
    at t (23-63969a852fd53b0b.js:2:17735)

I managed to load into the website today once, we might think it is an issue with cache, but we did the purge cache in cloudflare website and nothing changed.

The website is
https://kenabot.xyz/en

Peps•7/6/24, 8:11 PM

from what I can tell it has something to do with RSC I think?

[

[ ⚡ ] ElBretxa•7/6/24, 8:12 PM

We do not use RSC

[[ ⚡ ] ElBretxa We do not use RSC

Peps•7/6/24, 8:16 PM

hm your page's response does seem to indicate RSC is being used

[

[ ⚡ ] ElBretxa•7/6/24, 8:18 PM

we only use client components, with next v14 you must have enabled RSC by default

Peps•7/6/24, 8:24 PM

probably best to create a help thread in #general-help and continue there

[

[ ⚡ ] ElBretxa•7/6/24, 8:24 PM

Thanks

PPeps hm your page's response does seem to indicate RSC is being used

Isaac McFadyen•7/6/24, 9:34 PM

Out of curiosity: how can you tell between RSC and client components there?

Isaac McFadyen•7/6/24, 9:34 PM

I'd be able to tell it's Next but that's it

IIsaac McFadyen Out of curiosity: how can you tell between RSC and client components there?

Peps•7/6/24, 9:41 PM

from what I could find, both the connection closedconnection closed error and self.__next_fself.__next_f are coming from Next.js' RSC

JellyMuffin•7/7/24, 6:19 AM

Requiring users to enter their new password twice before changing it is a good practice. Since the password field is masked, users might not notice if they make a typing error. Confirming the password helps prevent mistakes.

JJellyMuffin Requiring users to enter their new password twice before changing it is a good p...

JellyMuffin•7/7/24, 6:20 AM

ömer•7/7/24, 10:39 AM

Hey, a few months ago I contacted to Cloudflare Galileo team for our application but then I lost our conversation and I can't find it now. I tried to contact Galileo through their landing page but now I don't get any responses. Can someone from CF help me contact Galileo again?