CORS on rate limit 429

Im getting this too. Anytime we get a 429 or 502 from Cloudflare, we have no way of catching this and showing the user a proper error message.

Considering moving to a self hosted NGINX if there’s no way to control this. Seems like a critical feature.