Worker path matching and query params conundrum

I'm seeing a lot of issues related to this and no real solution.

The problem is very simple and common:

I need something like

example.com/a

example.com/a

example.com/a

example.com/a as a trigger for my worker, including any query strings or hashes in the url.

Some solutions I see commonly given and what is wrong with them:

use
```
example.com/a*
```
example.com/a*
```
example.com/a*
```
example.com/a*
- this will match also other paths like
```
example.com/about
```
  example.com/about
```
example.com/about
```
  example.com/about
  which is undesired
use
```
example.com/a/*
```
example.com/a/*
```
example.com/a/*
```
example.com/a/*
- this will not match
```
example.com/a
```
  example.com/a
```
example.com/a
```
  example.com/a
  and neither it will match any query strings, unless there is a trailing slash in the url
I tried using
```
example.com/a?*
```
example.com/a?*
```
example.com/a?*
```
example.com/a?*
trigger but this one will throws an error "Route pattern should not have query parameters"

So can someone please help me and explain why is this such a problem for something that should be very common? Thanks.

No replies yetBe the first to reply to this messageJoin

Worker path matching and query params conundrum

Similar Threads

Similar Threads

Similar Threads