#31928: Coroutine passed to the first middleware's process_response() instead of
HttpResponse.
----------------------------------+------------------------------------
Reporter: Kordian Kowalski | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 3.1
Severity: Release blocker | Resolution:
Keywords: async asgi | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Kevin Michel):
I think it's a bug in SecurityMiddleware : its __init__ does not call
super().__init__().
This causes MiddlewareMixin._async_check() to not be called during init
and the
_is_coroutine magic attribute to be missing despite the async_capable=True
declaration.
--
Ticket URL: <https://code.djangoproject.com/ticket/31928#comment:3>
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.66e9f1ca03ec484748aab67f8379c9bb%40djangoproject.com.
