Community Forum
Localize SDK fails to load with crossorigin="anonymous" due to missing CORS headers
15 days ago by Gigi
We need to be able to load https://global.localizecdn.com/localize.js using crossorigin="anonymous" so browser error handlers receive detailed stack traces. Browser GET requests currently return HTTP 200 without Access-Control-Allow_origin, it causes the SDK to get blocked. We have also observed inconsistent CORS headers across CDN/cache responses. Can you enable Access Control Allow Origin * consistently for the SDK and its dynamically loaded scripts and confirm that anonymous CORS loading will be supported?
