Sounds more like a crappy setup than a problem with uWSGI itself. No. As I detailed, it was a deficiency with uWSGI itself. Complicating the setup as you sug

Sounds more like a crappy setup than a problem with uWSGI itself. No. As I detailed, it was a deficiency with uWSGI itself. Complicating the setup as you suggest is a crappy workaround for a uWSGI deficiency. We simplified the setup by switching to gunicorn. I would still use uWSGI, but, as with all software/tools, I would be aware that it has a deficiency. uWSGI docs on production usage of HTTP functionality don't mention this issue so I wanted to let others know. https://uwsgi-docs.readthedocs.org/en/latest/HTTP.html?highlight=http#can-i-use-uwsgi-s-http-capabilities-in-production https://uwsgi-docs.readthedocs.org/en/latest/HTTP.html?highl... I have a drawing of my favorite infrastructure Wish I had the luxury. We're running 20-30 projects/applications (~3000 tasks) across our clusters. Some are Django fronted by gunicorn, some are directly fronted by flask, but 80% are non-HTTP services.