Return helpful error message when CSRF protection fails. (#5177) #5182
Conversation
* Return helpful error message when CSRF protection fails. Before this change, the server returned a generic "Bad Request" error message when a client queried the API without the required CSRF protection header. This leaves the consumer confused, especially for previous users of the API which now do not know what to change in their request to make it work again. This change now leaves the error code intact but adds a helpful message telling the consumer what went wrong. Fixes #5012. * Making error message _even more(!)_ helpful.
|
Fixes #5012. |
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.
Port of #5177 into 2.5.