This repository has been archived by the owner on Jan 7, 2018. It is now read-only.
Add the ability to modify response headers (can be used for CORS setup) #9
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
GUI
added a commit
that referenced
this pull request
Mar 29, 2015
Add the ability to modify response headers (can be used for CORS setup)
GUI
added a commit
that referenced
this pull request
Jul 27, 2015
Implement new HTTPS requirement behavior
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a generic implementation of modifying response headers at the proxy layer which can be used t force CORS headers.
Related to 18F/api.data.gov#120 and NREL/api-umbrella#81