You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there :)
I'd like to know you about this situation and this is just a suggestion.
I happened a similar problem in case #2383
I set AllowAny permission, and DRF returns an Unauthorized 401 response.
The reason is If you call API with Authorization property such as Authorization: Bearer null[0], It return 401.
Regardless of whether there is Authorization property or not, should we consider not causing 401 in AllowAny permission?
[0]
The text was updated successfully, but these errors were encountered:
AllowAny tries to verify the token if it exists, if it doesn't exist, it moves on. Passing a null value would raise a 401 as expected, the way I see it, you just shouldn't pass the token if it's not valid
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi there :)
I'd like to know you about this situation and this is just a suggestion.
I happened a similar problem in case #2383
I set AllowAny permission, and DRF returns an Unauthorized 401 response.
The reason is If you call API with
Authorization property
such asAuthorization: Bearer null
[0], It return 401.Regardless of whether there is
Authorization property
or not, should we consider not causing 401 in AllowAny permission?[0]

The text was updated successfully, but these errors were encountered: