fix anonymous access for DjangoModelPermissionsOrAnonReadOnly #9315
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
|
Is it possible to add some tests to verify this? |
Yes. I've included them in the latest commit |
|
Superseeded by #9332, which instead outright reverts the change. |
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 pull request fixes anonymous read-only access for the
DjangoModelPermissionsOrAnonReadOnlyclass inpermissions.pyas mentioned in issue #9299.If the user is authenticated, it will run the the
has_permissionmethod defined inDjangoModelPermissionssince it's the parent class. If the user is not authenticated, then the user will have permission only if the method is safe. (GET, HEAD, or OPTIONS)