#37025: RemoteUserMiddleware.header does not correspond to request.META in the
async path
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
| Walls
Type: Bug | Status: assigned
Component: contrib.auth | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
RemoteUserMiddleware |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* needs_better_patch: 1 => 0
Comment:
Thanks Sarah for exploring that angle. I'm worried we're mixing a couple
things together here. Mykhailo found an existing bug during the review of
my PR, which I've now fixed. We shouldn't use that as a justification for
duplicating the middlewares, which is as disruptive as what Carlton winced
at in comment:5.
I've updated my [https://github.com/django/django/pull/21079 PR], and
think it's ready for another look.
--
Ticket URL: <https://code.djangoproject.com/ticket/37025#comment:18>
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/0107019de0ba295b-c980c58f-49ba-4e64-b882-22a6003524bd-000000%40eu-central-1.amazonses.com.
