CDN on Spaces omits CORS headers

Posted April 12, 2018 3.7k views
Arch LinuxCDN

When I get an object from Spaces through a CDN endpoint there’s no CORS headers (they are OK when I get the same object directly). Is it a DigitalOcean CDN issue?

1 comment
  • Is this still an issue? I’ve been going mad for the last 2 days over this.

    When I perform a HEAD request for a resource at the origin it’s fine, but when I perform a HEAD request on the same resource via the CDN I get this error:

    Access to XMLHttpRequest at ’…’ from origin ’…’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
6 answers

Same thing. I’m still getting CORS error when using fonts, delivering through the CDN

Thanks for reporting this. Our engineering team is aiming to take a look at it soon.

Please standby and thanks for your patience so far. We are close to announcing a fix for this.

The CORS issue was fixed on October 24th, 2018 and should now pass CORS headers through the CDN.

Getting CORS issue with fonts.

Has the problem been fixed? I’m taking cors error via cdn url.