#36200: Mention that RemoteUserMiddleware should be replaced when using custom
header middleware with RemoteUserBackend
-------------------------------------+-------------------------------------
Reporter: Joonas Häkkinen | Owner: Joonas
Type: | Häkkinen
Cleanup/optimization | Status: closed
Component: Documentation | Version: 5.1
Severity: Normal | Resolution: fixed
Keywords: REMOTE_USER, | Triage Stage: Ready for
authentication, middleware | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"aadc5c569bdf73d9e358c4371f7da18a0410234c" aadc5c5]:
{{{#!CommitTicketReference repository=""
revision="aadc5c569bdf73d9e358c4371f7da18a0410234c"
[5.2.x] Fixed #36200 -- Clarified MIDDLEWARE setting updates when using a
custom RemoteUserMiddleware.
Backport of 87c5de3b7f2316aa17353d74f54e6ff19013d049 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36200#comment:7>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019523ed6f3d-3b39d9c9-389d-4f2e-8079-6ba0d943bed2-000000%40eu-central-1.amazonses.com.
