> On May 20, 2013, at 12:22 PM, André Cruz <[email protected]> wrote: > >> On May 20, 2013, at 12:17 PM, Roberto De Ioris <[email protected]> wrote: >> >>> I think it is better to add a condition when the backend closes the >>> connection: if content_length is not completely read, just close the >>> connection independently by the keepalive status. >> >> I've also noticed that requests with CONTENT_LENGTH > 0 fail with a >> timeout if I comment out that line: >> >> [uwsgi-body-read] Timeout reading 16384 bytes. Content-Length: 4194304 >> consumed: 0 left: 4194304 >> >> So there is more going on here than I had imagined... > > If I comment: > > if (hr->session.can_keepalive) { > main_peer->disabled = 1; > // stop reading from the client > if (uwsgi_cr_set_hooks(main_peer, NULL, NULL)) > return -1; > } > > the request is correctly read. But the next request on the same connection > takes http-timeout seconds to be processed. > > André > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
Keep-alive on request with body shoulw now work. Remember: every parsing error (both on request and response) will close the connection -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
