Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Is possible to connect a DO K8s cluster with a DO Droplet private network? Question Question
Are there free accounts for non-profits? Question Question

Question

No 'Access-Control-Allow-Origin' header is present on the requested resource.

Posted July 10, 2020 48.1k views
PostgreSQLJavaAngular

Access to XMLHttpRequest at ’http://139.59.7.239:8080/home/properties’ from origin ’http://roostent.com’ has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

Add a comment
supportbc1965e07fd043df06e
By:
supportbc1965e07fd043df06e

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Is possible to connect a DO K8s cluster with a DO Droplet private network? Question Question
Are there free accounts for non-profits? Question Question

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
1 answer
KFSys July 11, 2020

Hi @supportbc1965e07fd043df06e,

Looks like your application or droplet does not include the Access-Control-Allow-Origin header in response to a preflight request (OPTIONS). A CORS request will fail if Access-Control-Allow-Origin is missing.

Having said that, to further provide any information about it, we might need more information. The issues itself could be of something really simple.For example, I was using die('message'); in a Laravel method and I received a CORS complaint, despite the CORS being whitelisted. After changing the response to just be return ['status' => 'success']; which formats over into JSON to the FE - problem solved. Curious if this may be the issue for some of you too. :)

Regards,
KFSYs

Reply Report

Related

Looking for something else?

Ask a new question Search for more help