[Security] Replace 403 with 401 in onAuthenticationFailure method
#35606
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
chalasr
approved these changes
Feb 5, 2020
|
Note for mergers: When merging this up to master, the patch should be applied to the |
|
Thank you @alanpoulain. |
nicolas-grekas
added a commit
that referenced
this pull request
Feb 5, 2020
…ure` method (alanpoulain) This PR was merged into the 3.4 branch. Discussion ---------- [Security] Replace 403 with 401 in `onAuthenticationFailure` method | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | N/A | License | MIT | Doc PR | N/A This comment in `onAuthenticationFailure` was misleading since a 401 status code should probably be returned instead of a 403. Commits ------- 73bc793 Replace 403 with 401 in onAuthenticationFailure method
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.
This comment in
onAuthenticationFailurewas misleading since a 401 status code should probably be returned instead of a 403.