Yeah okay cool

yeah sorry I clarified in the edit but it was too late lol

My understanding is they are entirely different internally. Routes are way more flexible (you can subpath matching, wildcards, etc). Custom Domains have other special features as well, like you are supposed to be able to fetch from a same-zone custom domain which you can't with routes (I think that's broken right now though)

Custom Domains are supposed to be an actual normalish origin

So if you only want the Cloudflare worker on it then use a Custom Domain, and if you've got a third-party service on it then use a Route. Right?

That's what I'm gathering, though I'm still a bit confused.

So if you only want the Cloudflare worker on it then use a Custom Domain, and if you want your worker run in front of an existing origin (changing the response, running only on a subpath, etc), use routes

I think that's a fine way to view it. There is a few other cases, like how Custom Domains let you run workers on 2nd level or deeper subdomains because they give you a free cert

That code James sent doesn't work with a Route. Only works with a Custom Domain. This is the part I'm trying to understand. Would a Route require a DNS record?

And a Custom Domain would automatically add it?

If it works with a custom domain, it'll work on a route too (besides same-zone fetches to another worker). You just need to manually create a DNS Record (use AAAA target 100:: proxied)

Yes, that's one thing Custom domains do, create the dns record for you

Right. I think I've got it.

So for the code James sent I need it on both so it includes the path?

Or can I get rid of the Route?

Does the Custom Domain cover paths?

Custom domain is like a normal dns record/origin, it covers all paths

Get rid of the route, it's one or the other

How many certificates does it deploy??

1 Advanced or 2 Advanced?

Each Custom Domain has its own adv. cert

Should just be one, you can see it under your zone's ssl/tls -> edge certs

Yeah I've got 2. Will delete one.

Did you create and delete a custom domain or something? It should only be one. It doesn't clean them up after you delete the custom domain though

I would be uhh careful about what you delete lol

It made 2 for some reason.

I've sorted it I think.

I think I broke it.

Or maybe it takes a while.

It can take a bit. You don't need it eitherway, your universal already covers it. Your custom domain should already be working