> On May 17, 2013, at 7:26 PM, Roberto De Ioris <[email protected]> wrote: > >> >> basically if there is a content_length the keepalive is disabled. >> >> I need only to double check if there was some reason to brutally drop on >> Content-Length or if it is a bug. > > I've removed that line and indeed the connection is kept alive. I've tried > multiple requests and they worked. But I don't know if there is some > internal uWSGI limitation for the previous behaviour... > > André > _______________________________________________ >
Ok, now i remember: basically if the backend closes the connection (for example because the content_length is higher than --limit-post) the webserver will think upcoming data will be the next request (while they are the body of the previous one). 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. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
