> Hi, > > We are running uwsgi in production since this morning, and it's > impressive how performance improved and system load climbed down. So > this was a good move, we are very happy about it, kudos for developing > this piece of OSS. > > However I'm a bit worried by some requests that result in an empty > response. I don't know what is causing this: either the uwsgi > application, or nginx's uwsgi support (version 0.8.49). This is a new > problem, I've never had empty responses with Flup. And interesting to > note: haproxy, which comes first in the HTTP chain, times out waiting > for the response. > > The status codes are OK: either 200 or 302 depending on what the > application replied, but response has zero bytes, at least according > to the Nginx logs. > > In my records, 113 requests out of 400000 failed like this. There are > no error printed in uwsgi's output. > > Any idea? > -- > Jean-Baptiste Quenot > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
Client send request -> nginx send request to uWSGI -> uWSGI/app set status code (and probably some header) -> client disconnect -> nginx close the socket with uWSGI -> uWSGI get broken pipe and a 0 response. uWSGI never buffer data (by default), it send data asap and stop the request at the first error. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
