Is it possible to route URLs ending in `/data/` to a worker, i.e. `https://example.com/*/data/`?

We want to do some custom processing on URLs which end in

/data/

/data/

/data/

/data/within a worker.

e.g.

POST https://example.com/foo/data/

POST https://example.com/foo/data/

POST https://example.com/foo/data/

POST https://example.com/foo/data/

POST https://example.com/foo/bar/data/

POST https://example.com/foo/bar/data/

POST https://example.com/foo/bar/data/

POST https://example.com/foo/bar/data/
etc.

kian•10/6/23, 3:56 PM

You can't do infix wildcards unfortunately

RichOP•10/6/23, 3:59 PM

I thought as much, thanks

Am I right in saying requests routed to a worker which are passed directly into fetch(request)fetch(request) would miss out on all of the Cache Rules we have setup? i.e.

fetch

fetch

will always go straight to origin?

RichOP•10/6/23, 3:59 PM

(I'm wondering whether we can do the URL routing in the worker directly)

kian•10/6/23, 4:01 PM

Page Rules behave like this with the Cache Level rule so I assume Cache Rules still work according to this matrix.

kian•10/6/23, 4:01 PM

Workers subrequests basically go through Cloudflare again.

RichOP•10/6/23, 4:05 PM

oh interesting

kian•10/13/23, 6:37 PM

kian•10/13/23, 6:37 PM

Looks like they currently don’t but that’s a big and they will soon

Is it possible to route URLs ending in `/data/` to a worker, i.e. `https://example.com/*/data/`?

Similar Threads

Similar Threads

Similar Threads