On Sep 12, 2012, at 7:36 AM, Roberto De Ioris <[email protected]> wrote:
> Having said that, you have to take in account it does not support advanced > features like http pipelining and keepalives. Shouldn't uwsgi's http module return the "Connection: close" HTTP header always since it does not support http pipelining/keepalives? I've seen cases where even though uwsgi sent a FIN after the first response, the browser sent another request in the same connection.... Best regards, André _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
