#29699: Remove redirect loop warning re. using redirect_authenticated_user with
permissions checking.
-------------------------------------+-------------------------------------
Reporter: brickl | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: 2.1
Documentation | Keywords: permission redirect
Severity: Normal | loop authenticate
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
As per [https://docs.djangoproject.com/en/2.1/topics/auth/default
/#redirecting-unauthorized-requests-in-class-based-views/ redirecting-
unauthorized-requests-in-class-based-views]:
**Changed in Django 2.1:**
In older versions, authenticated users who lacked permissions were
redirected to the login page (which resulted in a loop) instead of
receiving an HTTP 403 Forbidden response.
However, there is still a warning under
[https://docs.djangoproject.com/en/2.1/topics/auth/default/#all-
authentication-views/ all-authentication-views] that states that "Enabling
redirect_authenticated_user can also result in a redirect loop when using
the permission_required() decorator unless the raise_exception parameter
is used." This warning no longer seems to be relevant given the change
described above, and should be deleted.
--
Ticket URL: <https://code.djangoproject.com/ticket/29699>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.58dc3f1ff7b52db087e68a72b013f387%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.