# The Trouble With Middleware

**URL:** https://forum.djangoproject.com/t/the-trouble-with-middleware/19
**Category:** Async
**Created:** [September 9, 2019, 1:35am UTC](https://forum.djangoproject.com/t/the-trouble-with-middleware/19 "2019-09-09T01:35:49Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![andrewgodwin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/andrewgodwin/32/2_2.png) [@andrewgodwin](https://forum.djangoproject.com/u/andrewgodwin)
#### Post date: [January 28, 2020, 8:32pm UTC](https://forum.djangoproject.com/t/the-trouble-with-middleware/19/11 "2020-01-28T20:32:17Z")

</div>

Just thought I’d come back here and cap this off with the news that a redesign of how middleware operates lets a piece of middleware be both async- and sync-capable simultaneously, making this problem very tractable! We can likely port all of Django’s shipped middleware to this model without too much effort.

---

_[View the full topic](https://forum.djangoproject.com/t/the-trouble-with-middleware/19)._