On May 21, 2013, at 6:27 AM, Roberto De Ioris <[email protected]> wrote:
> Keep-alive on request with body shoulw now work. > > Remember: every parsing error (both on request and response) will close > the connection I've been testing this, and it seems to work most of the time (when it didn't, I think it was a client problem). I just have some questions: - Pipeline mode is not supported at all by the http plugin, right? I've noticed that uWSGI explicitly disables keepalive and closes the connection after the response when it detects the client has sent more data than the size of the body. - Right now I'm manually adding the “Connection: Keep-Alive” header through the uWSGI config. But sometimes this will not be true, as in the pipeline case. Can't uWSGI handle this header for me? Only uWSGI knows for sure if it will maintain the connection open or not. There are cases in which I respond early to the client with a 4XX error without reading the whole request from wsgi.input, uWSGI detects this and closes the connection but the header "Keep-Alive" is sent as well which is also not true. Btw, Django and other frameworks won't let me add the "Connection" header since they claim that it the web server responsibility. Thanks! André _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
