Roberto De Ioris <roberto@...> writes: > Hi, if you have not enabled --pep3333-input wsgi.input is a simple socket, > so you do not have to read more than CONTENT_LENGTH bytes (so read() will > block undefinetely). > > --pep3333-input instead will map wsgi.input to a custom object that > returns (in python3.x) bytes and allows read() and read(-1) without > blocking. >
Thanks, updating to 0.9.7.2 and adding --pep3333 solved this particular issue, however my original point still stands: How can i get detailed information about 500 errors originating from uWSGI in case if process is daemonized and there is nothing in the logs? _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
