What are the ports/URLs used by Cesium Ion imagery/terrain

Hi there, I was wondering what urls/ports were used to access the default imagery and terrain layers in Cesium ION, as well as any user uploaded layers.

We need to find out to add access to Cesium imagery and terrain through a corporate firewall that almost completely restricts access to the internet.

I assume ports are just 80 and 443?

1. A concise explanation of the problem you're experiencing.
Unable to access Cesium imagery/terrain through a corporate firewall.

2. A minimal code example. If you've found a bug, this helps us reproduce and repair it.
N/A, just the standard hello world cesium sandcastle.

3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
Need to allow access to the cesium imagery/terrain provider through a corporate firewall.

4. The Cesium version you're using, your operating system and browser.
1.45

By default, all content is requested at ‘https://api.cesium.com/’, though I am not sure if it’s a specific port.

Yes, the standard ports (80 and 443) should be all you need.

When loading the hello world cesium sandcastle and modifying it to use my key I noticed that when scrolling around a lot of tiles were coming in from URLS like:
blob:https://cesiumjs.org/eb4d4f86-da78-4828-9503-401aa943744c

and

https://ecn.t2.tiles.virtualearth.net/tiles/a03200321.jpeg?g=6465

Additionally, I saw terrain requests to:

https://assets.cesium.com/1/7/62/90.terrain?v=1.0.0

Are these URLs just sandcastle-specific?

https://ecn.t2.tiles.virtualearth.net/tiles/ is Bing Imagery.

blob:https://cesiumjs.org/eb4d4f86-da78-4828-9503-401aa943744c I believe is Sandcastle specific.

https://assets.cesium.com/1/7/62/90.terrain?v=1.0.0 is terrain from Cesium ion.

Can you allow urls at *.cesium.com?

All urls that start with “blob:” are local to the app, so there’s no need to worry about these in regards to the firewall. Cesium reads imagery tiles as blobs in a variety of cases, either to work around HTTP header limitations or in Bing’s case to look for sentinel values of “no data” tiles.

https://assets.cesium.com is where all of the actual ion tiles are hosted, so you’ll need to allow at least both api.cesium.com and assets.cesium.com through your firewall. (I would recommend *.cesium.com if you can get away with it for future proofing).

https://ecn.t2.tiles.virtualearth.net/tiles/a03200321.jpeg?g=6465 These are Bing Maps imagery tiles. While the initial handshake is through Cesium ion, Microsoft still serves the Bing tiles directly. If you previously allowed Bing Maps through your firewall with older versions of Cesium then you are good to go. If you are setting up the firewall for the first time, you’ll need to allow *.virtualearth.net (which is the official Microsoft endpoint) but you might be able to lock it down tighter than that. I don’t know offhand what the minimum is; but if you have trouble let us know.

I also wrote up an issue in our ion github repository so that we create an official FAQ for this: https://github.com/AnalyticalGraphicsInc/cesium-ion-community/issues/11

Awesome, thanks very much for the help guys!