add support for CORS headers #172
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added CORS support as a configurable option that can be enable or disabled. It is disabled by default to maintain backward compatibility. * When CORS is enabled... * Adds CORS response 'Access-Control-Allow-Origin' for all GET requests * Handles OPTIONS method requests for supported routes and responds with supported methods and allow origin header * When CORS is disabled... * The 'Access-Control-Allow-Origin' header is not added to GET requests * If OPTIONS method is requested, a 501 (not supported) response is returned REF: https://fetch.spec.whatwg.org/#http-cors-protocol
awead
approved these changes
Aug 31, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
REF: https://fetch.spec.whatwg.org/#http-cors-protocol