Ensure CORS headers get added to failed responses #4524
Merged
Conversation
This file contains hidden or 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
If an action fails due to an exception being thrown, the headers still need to be added so that the cross origin client can process the failed response.
cchantep
added a commit
that referenced
this pull request
May 21, 2015
Ensure CORS headers get added to failed responses
Member
|
In case there is another RC I think it would be nice to have this in |
marcospereira
added a commit
that referenced
this pull request
Jun 15, 2015
Backport of #4524 - Ensure CORS headers get added to failed responses
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
If an action fails due to an exception being thrown, the headers still need to be added so that the cross origin client can process the failed response.