[MGNLREST-269] Make CORS easier to Configure Created: 26/Aug/20  Updated: 09/Feb/21  Resolved: 09/Feb/21

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MAGNOLIA-7215 CORS & OPTIONS Pre-flight support Closed
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)

 Description   

User story:

As a Developer, CORS does not get in my way, and I can easily configure it to match the most common use cases.

Capabilities:

  • Easily configure which origins can request resources.
    • TBD: On a project, site, endpoint, or API key basis? Or on all of them?
  • Consider opening CORS to all sites in development mode. 

Context:
Currently must be configured in filter chain and with voters which is hard, error prone, and risk to mess up the filter chain.
This should be an easy thing to configure.
 



 Comments   
Comment by Christopher Zimmermann [ 09/Feb/21 ]

Fixed with MAGNOLIA-7215

Generated at Mon Feb 12 06:58:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.