Worker not triggered on route

For Workes & Pages, what is the name of the domain?

https://archiedev.co/yugbkjhb-94/sign-in

What is the error number?

N/A

What is the error message?

N/A

What is the issue or error you’re encountering

The worker is not being triggered on route archiedev.co/files-v2/*

What steps have you taken to resolve the issue?

  1. I have setup the worker route to be archiedev.co/files-v2/*
  2. I expected to see logs when triggering the worker route but none appear.
  3. I then tried going directly to the *. workers.dev URL and I see logs appear for the worker.
  4. I have verified the network-call host matched the worker route

What are the steps to reproduce the issue?

  1. Load the page https://archiedev.co/yugbkjhb-94/sign-in
  2. Open developer tools and see the network call meow_hungry.png to https://archiedev.co/files-v2/spaces/....
  3. Notice it matches the worker route archiedev.co/files-v2/*
  4. I have looked at the worker logs and none appear.
  5. I go to the worker *. workers.dev URL and I see logs appear

Can someone please tell me, what is wrong? Why is the worker not being triggered on its route but is triggered directly on *. workers.dev?

archiedev.co is not proxied so requests are going direct to your origin and not through Cloudflare. www.archiedev.co is proxied…
https://cf.sjr.dev/tools/check?0a8b78e97c5a4d409ca42db2f35d54d5#dns

2 Likes