Hey everyone! Are there any plans to allow query parameters via route patterns without also applying

Hey everyone! Are there any plans to allow query parameters via route patterns without also applying the wildcard to the path? For example:

example.com/page*

example.com/page*

example.com/page*

example.com/page* is the only way to support

https://example.com/page?blah=1

https://example.com/page?blah=1

https://example.com/page?blah=1

https://example.com/page?blah=1, but it also matches

https://example.com/page1234

https://example.com/page1234

https://example.com/page1234

https://example.com/page1234. This seems like a pretty serious limitation.

Ffrank Hey everyone! Are there any plans to allow query parameters via route patterns w...

sathoro•11/30/23, 2:32 PM

it's not possible to match the ?

Ssathoro it's not possible to match the ?

frankOP•11/30/23, 2:33 PM

It returns an error saying query strings aren’t allowed in the pattern.

Ffrank Hey everyone! Are there any plans to allow query parameters via route patterns w...

Chaika•11/30/23, 2:39 PM

There's been nothing mentioned about them changing soon and Worker Routes haven't changed in a while, that's also a documented limitation:
https://developers.cloudflare.com/workers/configuration/routing/routes/#matching-behavior

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

So I doubt it would change anytime too soon.
It's not the most optimal solution but you could parse the URL in the Worker and check if the pathname equals the one you're looking for, otherwise just passthrough return fetch(request)return fetch(request) the request, wouldn't interfere with anything but would cause Worker Invocations still

Routes · Cloudflare Workers docs

Routes allow users to map a URL pattern to a Worker. When a request comes in to the Cloudflare network that matches the specified URL pattern, your …

Chaika•11/30/23, 2:42 PM

Depending on how your website is setup, you could also potentially take advantage of the more specific matching behavior. If it's something like you want /post?ggg /post*/post* to go to a worker but not /posts?ggg, if you made a route for /posts*/posts* service none, that should be more specific and stop the Worker from running on that path

frankOP•11/30/23, 2:54 PM

Thanks - just wanted to see if anybody has heard anything about a change. Appreciate the reply

crossbeau•11/30/23, 7:51 PM

is anyone here using Nuxt/NitroServer with Service Bindings on their worker?

Miixms•11/30/23, 8:14 PM

question about the workers.. styandard requests

Miixms•11/30/23, 8:14 PM

i upgraded to premium, is it unlimited now?

Unsmart•11/30/23, 8:21 PM

If by "premium" you mean workers paid, then yes you can do an unlimited number of requests.

10 million requests included + $0.30/million after
30 million cpu milliseconds included + $0.02/million after

Miixms•11/30/23, 8:22 PM

cant i just higher my subscription to not have additional pay

Unsmart•11/30/23, 8:23 PM

I mean enterprise plans give custom pricing but its not going to be you pay $x for fully unlimited requests and cpu usage afaik

Unsmart•11/30/23, 8:24 PM

So no you cant pay more for a flat rate there will always be usage based costs

UUnsmart If by "premium" you mean workers paid, then yes you can do an unlimited number o...

Miixms•11/30/23, 9:37 PM

well 10million is not much

Miixms•11/30/23, 9:37 PM

and 0.30/million is getting quick expensive

MMiixms and 0.30/million is getting quick expensive

Unsmart•11/30/23, 9:38 PM

Then I would suggest you use a server based approach because $0.30/million is just about the cheapest you will ever get especially since every other platform charges duration a function runs and cloudflare only charges cpu

Miixms•11/30/23, 9:39 PM

for 1.99 a month on a diffrent service i can get unlimited requests

Unsmart•11/30/23, 9:40 PM

Which platform? Sounds like a very big lie to me

Miixms•11/30/23, 9:40 PM

well i use cf workers for dns requests

Unsmart•11/30/23, 9:41 PM

What do you mean cf workers for dns requests?

Miixms•11/30/23, 9:41 PM

like 1.1.1.1

Miixms•11/30/23, 9:41 PM

but then for yourself

Unsmart•11/30/23, 9:41 PM

You mean like cloudflare warp?

Miixms•11/30/23, 9:42 PM

Unsmart•11/30/23, 9:42 PM

I mean cloudflare warp is 1.1.1.1 for personal use so what do you mean?

Miixms•11/30/23, 9:42 PM

just 1.1.1.1 only

Miixms•11/30/23, 9:43 PM

warp can be with proxy

Unsmart•11/30/23, 9:43 PM

Ok so what about 1.1.1.1 though? Its free for unlimited requests yeah but thats very different from what workers is

Miixms•11/30/23, 9:43 PM

yes

Miixms•11/30/23, 9:43 PM

exactly why workers is expensive for dns product hosting

Miixms•11/30/23, 9:44 PM

what can be used as 1.1.1.1

Unsmart•11/30/23, 9:44 PM

You dont use workers for dns though?

Miixms•11/30/23, 9:44 PM

lots of people do

Unsmart•11/30/23, 9:44 PM

Do you have an example of this?

Miixms•11/30/23, 9:45 PM

rethinkdns does

Miixms•11/30/23, 9:45 PM

but there are also github packages to launch on cf workers

Unsmart•11/30/23, 9:47 PM

Where do you see that rethink does their dns with cloudflare workers though? Their site is hosted on cloudflare sure but that doesnt mean they use workers for dns

UUnsmart Where do you see that rethink does their dns with cloudflare workers though? The...

Miixms•11/30/23, 9:48 PM

check their faq

Original message was deleted

Miixms•11/30/23, 9:50 PM

it can be 11k+ in a hour

Miixms•11/30/23, 9:51 PM

my stats

Unsmart•11/30/23, 9:52 PM

Their faq seems to say it just forwards to 1.1.1.1 or you use their fly stuff.

Rethink DNS is both a stub and a recursive resolver-- sky.rethinkdns.com forwards user requests to another recursive resolver like Cloudflare's 1.1.1.1, but does so in a way that doesn't leak the identity of the client (user). Think of it like a proxy resolver that sits in-between a recursive resolver and you, the user.

max.rethinkdns.com, which runs on fly.io is a recursive resolver and does not forward queries, but resolves DNS answers on its own.

But either way cloudflare workers are pretty much the cheapest option that exists for serverless compute. You can get enterprise plans which has custom pricing but no one here will be able to tell you what the pricing will be. If you dont want to pay that much per request then a server based option seems like a good solution for you

UUnsmart Their faq seems to say it just forwards to 1.1.1.1 or you use their fly stuff. >...

Miixms•11/30/23, 9:53 PM

lol, why would i get the enterprise plan for 200eur+ a month, if i can get it for 1.99

Original message was deleted

Miixms•11/30/23, 9:53 PM

devices are not sleeping

Miixms•11/30/23, 9:53 PM

iot

Unsmart•11/30/23, 9:54 PM

Then dont use cloudflare workers if you can get something cheaper?

Miixms•11/30/23, 9:54 PM

yes.. but it was worth the try

sathoro•12/1/23, 5:01 AM

switched to the "Smart" placement and immediately started getting 500 errors. switched it back within a minute and it went back to normal. is it expected for our Workers to temporarily stop working when we toggle on Smart placement?

kian•12/1/23, 5:01 AM

Was you tailing the Worker at the time?

Kkian Was you tailing the Worker at the time?

sathoro•12/1/23, 5:02 AM

no but we have Logpush

Hey everyone! Are there any plans to allow query parameters via route patterns without also applying

Similar Threads