You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Delivery-Service and Delivery-Dashboard are typically deployed in such a way that they are served from different (sub-)domains. Because this makes requests from Delivery-Dashboard cross-domain-requests, Delivery-Service needs to set "CORS-Headers". Currently, it sets those for any domain (*), which is not a recommended practise.
Implementation Proposal
Make domain(s) for which Delivery-Service set CORS-Headers configurable. Configure OCM-Gear-Installer such that it will by default restrict CORS-Domains to the one from which Delivery-Dashboard will be served. It should remain possible for users to overwrite this default.
The text was updated successfully, but these errors were encountered:
Context / Motivation
Delivery-Service and Delivery-Dashboard are typically deployed in such a way that they are served from different (sub-)domains. Because this makes requests from Delivery-Dashboard cross-domain-requests, Delivery-Service needs to set "CORS-Headers". Currently, it sets those for any domain (
*
), which is not a recommended practise.Implementation Proposal
Make domain(s) for which Delivery-Service set CORS-Headers configurable. Configure OCM-Gear-Installer such that it will by default restrict CORS-Domains to the one from which Delivery-Dashboard will be served. It should remain possible for users to overwrite this default.
The text was updated successfully, but these errors were encountered: