CORS problem on cesiumjs.org?

Since recently, I am getting CORS errors:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://cesiumjs.org/releases/1.40/Build/Cesium/Assets/IAU2006_XYS/IAU2006_XYS_15.json. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).

when running my Cesium app in my local dev enviroment. Has anything changed at your end?

Happy Holidays,

Klaus

I just realized this is somehow connected to changing my local domain from .dev to .local due to a name conflicht with the Google .dev domian resulting in NET::ERR_CERT_COMMON_NAME_INVALID. Still stunned why this is happening, though.

Hi Klaus,

We recently changed how we were hosting content for cesiumjs.org. The CORS configuration was wrong, but should now be correct for releases. Let me know if you are still having trouble.

Thanks,

Gabby

Unfortunately not. And access from my live pages is broken as well!

https://cesiumjs.org/releases/1.39/Build/Cesium/Cesium.js (or 1.40) gives

404 Not Found

  • Code: NoSuchKey

  • Message: The specified key does not exist.

  • Key: releases/1.39/Build/Cesium/Cesium.js

  • RequestId: 36BABC358EFA46FC

  • HostId: pnZ5uEIoA+2JhF82iyywaHDg4PeqoWRcwfTmXW836YOEzrDPyHr6i/eGaxu9TKoGoGWQK9MTkSk=

Sorry about that! The page is fixed now.

Thanks,

Gabby

Gabby,

I can confirm it’s working again – on my internal and external web serve.

Thanks for looking into this!

Klaus