CORS support
functionality to support CORS
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
- Implemented
- Milestone target:
- 1.7.5
- Started by
- John Dickinson
- Completed by
- John Dickinson
Related branches
Related bugs
Sprints
Whiteboard
From John:
First, of course, make sure it works and doesn't break any existing functionality.
Second, make sure you design your feature for large scale and multi-tenancy. I think that the CORS feature should be enabled and disabled on a container level.
Also, unless this feature has zero impact to existing clusters, then it should probably be able to be turned on and off in a config file. However, the toggle switch may or may not be needed depending on your implementation and the opinions of the other swift devs.
Finally, make sure that your patch is tested and documented. It should have unit tests, pass pep8, and include auto-generated docs that describe what's going on and how to use the feature.
Work Items
Work items:
Appropriately respond to http OPTIONS: TODO
Allow per-container Access-
Build toggleable support at a container level (defaulting to disabled should maintain zero impact to existing clusters): TODO
Create auto-generated docs: TODO
Create unit tests: TODO
Run and pass pep8: TODO