#37079: RemoteUserMiddleware assumes all ASGI requests will be handled by its 
async
path
-------------------------------------+-------------------------------------
     Reporter:  Jacob Walls          |                    Owner:  Jacob
                                     |  Walls
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.auth         |                  Version:  5.2
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  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:"0147222691db284f87c8c2a64ac6b1eded034c49" 0147222]:
 {{{#!CommitTicketReference repository=""
 revision="0147222691db284f87c8c2a64ac6b1eded034c49"
 Fixed #37079 -- Fixed specialization of header lookups in
 RemoteUserMiddleware.

 We need to switch on whether the request is a WSGI or ASGI request to
 know whether to prepend `HTTP_`: we cannot assume sync exceution means
 we are running under WSGI, as there could be other sync middleware
 forcing sync execution under ASGI.

 Thanks Mykhailo Havelia for the report.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/37079#comment:5>
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/0107019df424a033-a9295d81-3c21-4db3-8cc0-b3ee2eb3c5b6-000000%40eu-central-1.amazonses.com.

Reply via email to