Workers bot traffic / exposing workers.dev url in production
So I have two workers that I'm using at the moment, one purely for front end (migrated from pages) and one for a backend API/logic.
Is this the wrong pattern or architecture? Should it all be in one?
I got an email saying my API had a spike in bot traffic, and was wondering how to protect against that - and if I go to production is exposing the workers.dev url the way to do it, or how is it meant to be done?
Is this the wrong pattern or architecture? Should it all be in one?
I got an email saying my API had a spike in bot traffic, and was wondering how to protect against that - and if I go to production is exposing the workers.dev url the way to do it, or how is it meant to be done?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
