Opened 12 years ago
Closed 12 years ago
#19615 closed Uncategorized (wontfix)
Post Buffering with uWSGI
Reported by: | tompaw | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.4 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
This refs. https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/uwsgi/
Please add --post-buffering 1 to the list of default uwsgi parameters. Otherwise you might end up wasting half of your day, like I did today, until found this:
http://stackoverflow.com/questions/3970495/nginx-connection-reset-response-from-uwsgi-lost
This is over 2 years old now on Stack Overflow and apparently is still not handled by the latest version of uwsgi by default.
Django 1.4.3 + uWSGI 1.4.4 + nginx 1.2.6
Change History (2)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Agreed, I don't think it's Django's place to document this.
from the description of --post-buffering I am strongly -1 on it (http://uwsgi-docs.readthedocs.org/en/latest/Options.html#post-buffering). Saving post to disk is probably not a good idea as default.