Unable to Configure Static Assets & Worker Script Routing using `run_worker_first`
Hi we are in the process of porting our Astro.js website which is currently on Cloudflare Pages to Cloudflare workers by using the @astrojs/cloudflare plugin and are facing a issue w.r.t how cloudflare static asset routing which is shooting up our overall workers bill.
Being a static site generator, Astro.js outputs
---
Our use case requires the use of Astro's Middleware feature to run on specific routes. Since the middleware's default behaviour is to run on all routes, a worker invocation is triggered on every request that does not match a static asset, i.e. a
A) Routes that we want to hit the middleware e.g.
B) Non-existent routes leading to a 404 not found error
As of now, there is no provision in the Astro middleware to run on specific routes, like on other frameworks such as Next.js.
---
Case B) is causing thousands of worker invocations on our current staging Astro website. The majority of these requests are coming from malicious bots and crawlers looking for sensitive files such as
Hence we are trying to find a solution that allows the Astro middleware worker script to run only on Case A), i.e. only on explicitly whitelisted paths.
Being a static site generator, Astro.js outputs
index.html./dist/_worker.js/index.js---
Our use case requires the use of Astro's Middleware feature to run on specific routes. Since the middleware's default behaviour is to run on all routes, a worker invocation is triggered on every request that does not match a static asset, i.e. a
index.htmlA) Routes that we want to hit the middleware e.g.
/oauth/callbackB) Non-existent routes leading to a 404 not found error
As of now, there is no provision in the Astro middleware to run on specific routes, like on other frameworks such as Next.js.
---
Case B) is causing thousands of worker invocations on our current staging Astro website. The majority of these requests are coming from malicious bots and crawlers looking for sensitive files such as
.env.htaccessHence we are trying to find a solution that allows the Astro middleware worker script to run only on Case A), i.e. only on explicitly whitelisted paths.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,801Members
Resources
Was this page helpful?
