Access-control-allow-origin CORS Header not honoring System setting Configuration
Written By
Jorge García Jiménez
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- When configuring CORS headers in System Settings we are seeing that access-control-allow-origin header doesn't always have the configured value.
Resolution
- According to the specification, if the request is valid for cors and it has a "Origin" header, this value will be set as access-control-allow-origin in response headers instead of the value set in the configuration.
This is what the specification states:
Limiting the possible Access-Control-Allow-Origin values to a set of allowed origins requires code on the server side to check the value of the Origin request header, compare that to a list of allowed origins, and then if the Origin value is in the list, set the Access-Control-Allow-Origin value to the same value as the Origin value.
Did this article resolve your issue ?