A solution could be to use Cloudflare Worker scripts. You would store valid file names in their kv storage and then check if the incoming request is valid befor

A solution could be to use Cloudflare Worker scripts. You would store valid file names in their kv storage and then check if the incoming request is valid before forwarding it. This way you wouldn’t need to spend more money on infrastructure. Another good solution is to use Cloudflare’s advanced rate limiting rules. You can block users who hit too many 404 requests within a certain time frame. But this requires a business or enterprise plan. Spending more money on increasing infrastructure rather than reading through Cloudflare’s documentation and offerings seems kind of a waste…