Change Nitro to fetch from CDN in the browser, not the server

[cmeeren]

Product

Nitro

Is your feature request related to a problem?

When the Nitro app is requested from the server, the server calls out to cdn.chillicream.com (previously cdn.bananacakepop.com). In some environments, this requires these URLs to be explicitly whitelisted for outgoing traffic. This originally caused us some confusion and wasted hours with HotChocolate 13, and now with the latest 14 RC, it caused us some confusion again since the UI stopped working due to switching to cdn.chilicream.com (which we then had to whitelist).

The solution you'd like

Instead of the server fetching the UI from CDN, it would be easier if the browser did it. That would avoid these issues.

[kellerd]

Just went down this rabbit hole myself.

The default behaviour in this case was:

• The call would be denied by the firewall
• The connection would timeout
• .net core app service would think there was an issue starting the service and restart
• This will recursively restart the application