Code

#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

Attachments (0)

Change History (2)

comment:1 Changed 15 months ago by apollo13

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

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.

comment:2 Changed 15 months ago by timo

  • Resolution set to wontfix
  • Status changed from new to closed

Agreed, I don't think it's Django's place to document this.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.