Question

Spacess, CDN and CORS settings

Hey everyone :)

I’m still playing around using spaces for my web development and so far I really dig it.

However I’m facing an issue about using the right CORS setting, I’m not sure if it on DO space I need to set this or on my own server.

I’ve added 2 images, one with the CORS settng on DO and the next is the error.

https://i.gyazo.com/432b08f52c7291dfe5f60896086ed03a.png

https://i.gyazo.com/996371d9245584b7d2650edc4443a811.png


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Issue is that cross site access not allowed source cdn.rgb-profiles.xyz/font-awesome/fonts... We had a similar issue. Despite the fact that we loaded font awesome fonts from Droplet and not Spaces we got this error. That was due to relative link trying to load font from Spaces CDN. When we did set CORS at Spaces to allow access origin * we got a 404. We did however not want to use allow access origin all so we fixed the url and loaded from Droplet.

If you can set origin to specific location at Spaces CORS settings and do this for at least GET (PUT and POST probably not needed) that should get things working again. At least when fonts are on Spaces. And setting specific source (your website) will make it specific enough and thereby not inherently insecure.