CORS policy change this morning?

1. A concise explanation of the problem you’re experiencing.

We are getting (many) errors similar to following on Cesium load, and some functionality is not working :

Access to XMLHttpRequest at ‘http://cesiumjs.org/releases/1.58/Build/Cesium/Assets/approximateTerrainHeights.json’ from origin****** has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

Access to XMLHttpRequest at ‘http://cesiumjs.org/releases/1.58/Build/Cesium/Assets/Textures/SkyBox/tycho2t3_80_mx.jpg’ from origin ****** has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

3. Context. Why do you need to do this? We might know a better way to accomplish your goal.

It was working fine until yesterday. Starting this morning we are getting this error

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

We are using 1.58, but same behavior is in 1.60

Back to normal now!

But still still not working for test environment using localhost

There has indeed been a change, which has been reverted, see: https://github.com/AnalyticalGraphicsInc/cesium/issues/8050

Are you still having issues?

Out testing environment runs over HTTP and was loading Cesium over HTTP. And still fails if doing so.
Changing Cesium links to HTTPS fixed the issue