> Route pattern matching considers the entire request URL, including the query parameter string. Sin

Route pattern matching considers the entire request URL, including the query parameter string. Since route patterns may not contain query parameters, the only way to have a route pattern match URLs with query parameters is to terminate it with a wildcard, *.

https://developers.cloudflare.com/workers/configuration/routing/routes/#route-patterns-may-not-contain-any-query-parameters

CChaika > Route pattern matching considers the entire request URL, including the query p...

Luke•7/10/24, 5:35 PM

The problem with this is that if I only want to run the worker on the home page and I terminate the route with a wildcard it matches 100% of all URLS, not just the home page route

. E.G- it will match too

LLuke The problem with this is that if I only want to run the worker on the home page ...

ChaikaOP•7/10/24, 5:36 PM

yea, I get what you want, some people have asked for that before, it's just as the docs say though

ChaikaOP•7/10/24, 5:37 PM

if you a paid zone you could work around it with snippets (although they're alpha/not recommended for production yet), either doing the logic in a snippet directly or fetching a worker on a subdomain, and then they're powered by ruleset engine so you could have it check only if any query params are set (len > 0), or for a specific one, etc

CChaika CF For SaaS is your friend, you get 100 custom hostnames for free

whois | API man•7/10/24, 5:37 PM

oh, 100? and how much would cost more?

whois | API man•7/10/24, 5:37 PM

i think to begin with 100 is nice

Wwhois | API man oh, 100? and how much would cost more?

ChaikaOP•7/10/24, 5:37 PM

$0.10/per hostname/per month

CChaika $0.10/per hostname/per month

whois | API man•7/10/24, 5:38 PM

lol i think its cheap

whois | API man•7/10/24, 5:38 PM

anyways thanks!!

ChaikaOP•7/10/24, 5:38 PM

way cheaper then it was at one point yea, and if you get to a really large point you could get even potentially cheaper ent pricing like shopify and such

CChaika if you a paid zone you could work around it with snippets (although they're alph...

Luke•7/10/24, 5:38 PM

Got it, thank you

CChaika way cheaper then it was at one point yea, and if you get to a really large point...

whois | API man•7/10/24, 5:38 PM

ooo nice, hope i do

whois | API man•7/10/24, 5:39 PM

so basically the users can add my fallback origin to their dns

whois | API man•7/10/24, 5:39 PM

with this workers function

whois | API man•7/10/24, 5:39 PM

and it will consume my worker requests right?

Wwhois | API man and it will consume my worker requests right?

ChaikaOP•7/10/24, 5:40 PM

yes, although a point worth mentioning is you have to add them as a custom hostname (in dash or via api) first, and then they cname (or do the prevalidation first to avoid downtime) and get activated

CChaika yes, although a point worth mentioning is you have to add them as a custom hostn...

whois | API man•7/10/24, 5:41 PM

ye basically give them my the option to use my cname and if they want they can just validate their own

whois | API man•7/10/24, 5:41 PM

but

whois | API man•7/10/24, 5:41 PM

i think for my app it would be better to do prevalidation first

whois | API man•7/10/24, 5:41 PM

like on boarding

sarmaasis•7/10/24, 6:41 PM

Hi everyone,
I'm currently working on adding a custom domain feature to my project, and I could use some assistance. Here are the details of my setup:
I have an Angular site hosted on Cloudflare Pages with the following DNS settings for my domain (site.com):

I have enabled Cloudflare for SaaS and added "fallback.site.com" as the fallback origin for site.com.
I also have a domain (test.com) and have created a custom hostname (app.test.com). I generated a TXT validation and added the TXT record and a CNAME record (CNAME --- app --- cd.site.com) to the test.com DNS records.
Additionally, I have a worker that routes requests coming to site.com. The worker acts as a reverse proxy, serving content from either the Pages site or a WordPress site, while keeping the URL in the browser as site.com/*. However, when I try to handle the custom domain and serve a page from site.com/custom-domain, the URL in the browser changes from app.test.com to site.com/custom-domain.
Here I have attached index.js and wrangler.toml:

And here is the wrangler.toml configuration:

How can I ensure that the content of the pages is loaded while keeping the URL the same in the browser(app.test.com)? Any help or guidance would be greatly appreciated!
Thanks in advance for your help!

index.txt2.34KB

wrangler.txt359B

Nameless Monster•7/11/24, 12:24 PM

My Cloudflare Worker is blocking fetch requests originating from Vercel or Netlify. How can I stop this?

dsmith1024•7/11/24, 2:46 PM

can a tail worker be the same codebase as the original worker? like is it possible to just call the same workers fetch handler? I don't want to stand up a new worker right now and hoping to kinda hack it.

Also do they get triggered in local dev with wrangler?

dsmith1024•7/11/24, 3:35 PM

doesnt seem to be working, but im not quite sure how to tell honestly. Tailing the logs I dont see the tail worker called, but not sure if that would actually show.

brighter•7/11/24, 7:55 PM

anyone got to play nicely with workers?

brighter•7/11/24, 9:38 PM

nevermind; after battling it for an hour or so, i've decided to write a little wrapper around

console.log

console.log

Chris•7/11/24, 11:27 PM

Is there an easy way to tell if the worker is being served from wrangler dev? I have a use case where I want to know if the worker is actually deployed to allow/disallow localhost in CORS. Right now I'm using the CF-Ray header to detect this, but it doesn't work if the wrangler dev is using a remote deployment

NNameless Monster My Cloudflare Worker is blocking fetch requests originating from Vercel or Netli...

Cyb3r-Jak3•7/12/24, 12:07 AM

You should check your WAF logs. Probably where the request is being blocked.

dave•7/12/24, 2:44 AM

Iirc the cf object will only be present if served from CloudFlare. https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties

Cloudflare Docs

Request · Cloudflare Workers docs

Interface that represents an HTTP request.

Ddave Iirc the cf object will only be present if served from CloudFlare. https://devel...

Hello, I’m Allie!•7/12/24, 6:54 AM

It’s also present in local dev

Bbrighter anyone got `pino.transport` to play nicely with workers?

teaglebuilt•7/12/24, 12:53 PM

no but i cannot get kafka to work either

CCyb3r-Jak3 You should check your WAF logs. Probably where the request is being blocked.

Nameless Monster•7/12/24, 1:15 PM

Okk

HHello, I’m Allie!It’s also present in local dev

dave•7/12/24, 1:37 PM

Oops, never mind.

Sam•7/12/24, 3:13 PM

This basically means that smart placement is slower than the normal placement, or am I wrong? D1 database is hosted in East US and my service that's fetching data from this worker every minute is also located in the East of the US.

SSam This basically means that smart placement is slower than the normal placement, o...

ChaikaOP•7/12/24, 3:17 PM

If you have a D1 DB attached and you turn on Smart Placement, it overrides its location to be closest to the D1 DB, and D1 Requests aren't going to show up in any of the Request Duration/Subrequest charts I don't think

tornado•7/12/24, 11:16 PM

If I want to guard my api with a bearer token, is it better to use the cloudflare access or do the check in my middleware?

I was reading that cache api doesn't work behind cloudflare access, any other downsides? what about performance?

Ttornado If I want to guard my api with a bearer token, is it better to use the cloudflar...

Cyb3r-Jak3•7/13/24, 12:02 AM

You can check there is an API token with WAF rules and check the validity of the token in your middleware