-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTPBearer security scheme is returning 403 instead or 401 #10177
Comments
I use the |
Hey @Kludex, what do you think about raising a
My reading of this text is that:
|
Can you show me the diff you are talking about? |
EDIT: Wrong line sorry |
You want 400 instead of 403? That's why I asked the diff, not the lines in the code source. 👀 |
Sorry, my misunderstanding. At any rate, I don't think it is necessary after reading section 3 again I realised they offered an example for this scenario. tldr; 401 seems like the appropriate error code 👍
|
This not only affects the |
Discussed in #9130
Originally posted by aaaaahaaaaa September 8, 2020
HTTPBearer security scheme enabled as a dependency is returning a
403
when a request is unauthenticated because of a missing or a malformedauthorization
header. In those scenarios, a401
should be returned instead.Related PRs
The text was updated successfully, but these errors were encountered: