Workers not running on proxied subdomain routes that are app-owned?
I have a simple worker that generates a robots.txt allow-all.
It runs on two routes. One is *sygnal.com/robots.txt, where it runs fine.
Second is *assets.sygnal.com/robots.txt, where it does NOT execute.
The assets subdomain is managed by the 'Cassette' app, which basically maps an S3 bucket into the subdomain. I need to set the robots.txt to allow all.
Where is the conflict? How do I resolve it?
2 Replies
Cloudflare Apps and Workers have problems together, you would have to remove the App and can add its logic to your Worker instead
Thanks Erisa, so I'd have to redesign the app as a worker? I'd been considering that anyway, or build my own extended App version of cassette.
One of the frustrations I've been having is difficulty finding any formal diagram that explains how requests are routed across workers, apps, page rules, redirect rules, etc. It's been hard to design systems without a map that can help me choose the right place for each piece of functionality. Is there a diagram or a detailed writeup you can point me to?