#36862: Clarify RemoteUserMiddleware usage and deployment requirements under
ASGI
-------------------------------------+-------------------------------------
Reporter: Natalia Bidart | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: closed
Component: Documentation | Version: 6.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
RemoteUserMiddleware asgi | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"2ee757ee502d5663f932dc5c35175c39af4640ce" 2ee757ee]:
{{{#!CommitTicketReference repository=""
revision="2ee757ee502d5663f932dc5c35175c39af4640ce"
Fixed #36862 -- Doc'd the need for a proxy when deploying
RemoteUserMiddleware under ASGI.
We have a flood of nuisance security reports describing ASGI deployments
using RemoteUserMiddleware without a fronting proxy, which is not
realistic.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36862#comment:15>
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/0107019d4e590d6d-1f64009f-1268-40ee-82e5-abac5ced0488-000000%40eu-central-1.amazonses.com.
