Yes, it appears it does. I had turned it on for some reason I don't recall now. This works, though I think post-buffering should work.
Craig Younkins On Tue, Jun 7, 2011 at 1:31 AM, Roberto De Ioris <[email protected]> wrote: > > Il giorno 07/giu/2011, alle ore 07.44, Craig Younkins ha scritto: > > > I've been at this issue for literally days. Please help me! > > > > When I submit a large POST request, the uwsgi worker process that handles > it dies without any logging information. Nginx then issues a 502 when the > socket closes. Small POST requests work fine, and the issue starts with > something around 7000 bytes in the POST data. > > > > I believe it's related to post buffering. > > > > These are my current command-line options: > > DAEMON_OPTS="\ > > -s 127.0.0.1:9001 \ > > -M \ > > -t 0 \ > > -A 4 \ > > -p 1 \ > > --post-buffering 65536 \ > > -d /var/log/uwsgi.log \ > > --pythonpath $PYTHONPATH \ > > --module $MODULE" > > > > but I have tried with --post-buffering 1 and --pep3333-input, harakiri > mode on and off, with no success. > > > > U > > > Does it work without post-buffering ? > -- > Roberto De Ioris > http://unbit.it > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
