#31928: Coroutine passed to the first middleware's process_response() instead of
HttpResponse.
-------------------------------------+-------------------------------------
Reporter: Kordian Kowalski | Owner: Kevin
| Michel
Type: Bug | Status: closed
Component: HTTP handling | Version: 3.1
Severity: Release blocker | Resolution: fixed
Keywords: async asgi | 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 Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"3a42c0447b6a3187bd2aaae0bba566d835c47d22" 3a42c044]:
{{{
#!CommitTicketReference repository=""
revision="3a42c0447b6a3187bd2aaae0bba566d835c47d22"
[3.1.x] Fixed #31928 -- Fixed detecting an async get_response in various
middlewares.
SecurityMiddleware and the three cache middlewares were not calling
super().__init__() during their initialization or calling the required
MiddlewareMixin._async_check() method.
This made the middlewares not properly present as coroutine and
confused the middleware chain when used in a fully async context.
Thanks Kordian Kowalski for the report.
Backport of 825ce75faec63ce81601e31152c757a9c28fed13 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31928#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.f189e841ce88b36ae865b4d1d05fc649%40djangoproject.com.
