[busymom0]

One of the comments on the post is:

> One thing you could do in future is to url redirect any BunnyCDN url back to the clients original url, in essence disabling the CDN and getting your clients own hosts do what they were doing before they connected to BunnyCDN, yes it means our sites won't be as fast but its better than not loading up the files at all. I wonder if that is possible in technical terms?

Isn't this a horrible idea? If you use bunny, this would cause a major spike in the traffic and thus costs from your origin server.

[ev1]

Doing this if you are intentionally trying to protect or hide your origin is effectively guaranteed killing on the origin. For example, if Cloudflare unproxied one of my subdomains I'd leave them immediately, and likely have to change all my infrastructure and providers due to attacks.

This is also a terrible idea because of ACLs/firewalls only allowing traffic from CDN (this is extremely common for things like Cloudflare and Akamai) and relying on the CDN for access control.

[corobo]

Yeah please don't do this without me having checked a box to do that haha

There's a reason I use a CDN, let me decide if it's up or down if the CDN is down. If I want failover, I'll do that bit.

[dindresto]

Also, how would this work if their whole infrastructure is down? The same problem that prevented them from fixing the network would also have prevented them from adding such a redirect.