Context Navigation

Changes between Version 6 and Version 9 of Ticket #33716

-              v6
+              v9
 }}}
 This checks if the next middleware is a coroutine, and if not fallbacks to sync mode. However, we already mark all async-capable middleware as such, why the redundancy?
+This checks if the next middleware is a coroutine, and if not fallbacks to sync mode. However, I think this check is redundant: if the middleware is async-capable, and we have an ASGI request, what else we need ti check?
 A common usecase that is currently not supported:
+The downside of _async_check is that this common usecase is not supported:
 …
 middleware(request) will return the response in sync case and a coroutine in the async case, despite being a regular function (because get_response is a coroutine function in the latter case).
+So I propose to remove the redundant _async_check
+Here is a patch that I use that explains a possible way to fix it:
+Github project to see the error: https://github.com/pwtail/django_bug
+{{{
+def call_mw(mw, request, _call_mw=MiddlewareMixin.__call__):
+    if isinstance(request, ASGIRequest) and mw.async_capable:
+        return mw.__acall__(request)
+    return _call_mw(mw, request)
+MiddlewareMixin.__call__ = call_mw
+}}}
+Github project that shows the error: https://github.com/pwtail/django_bug