[MAGNOLIA-8644] CORS issues can be happen Magnolia (on premises) with a middle ware server Created: 22/Nov/22 Updated: 22/Nov/22 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Oanh Thai Hoang | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Date of First Response: | |||||
| Epic Link: | Headless Backlog | ||||
| Story Points: | 3 | ||||
| Team: | |||||
| Description |
|
Follow up from https://git.magnolia-cms.com/projects/CLOUD/repos/magnolia-cloud/pull-requests/717/overview?commentId=104782
I think we could face this issue again when we deploy Magnolia with a middle ware server (with cache), so we should add these headers in core products as well.
|
| Comments |
| Comment by Christopher Zimmermann [ 22/Nov/22 ] |
|
Just a note. With 6.3 we want to change our approach to CORS in that CORS should be open by default. CORS causes so much challenges for headless development, and I don't hear about anyone being very eager to use CORS for security. So we will make it "work by default" and then if a customer wants to restrict cross origin requests, then they can. |