> Hi, > > I'm running a Pyramid server through uwsgi and today I saw a couple of > exceptions (OSError: timeout during read(8192) on wsgi.input). All of > them were preceeded by failures like > > [uwsgi-body-read] Timeout reading 8192 bytes. Content-Length: 9784500 > consumed: 8683520 left: 1100980 > > Is this because the client's connection drops and the request is > incomplete?
yes > > Is there a more graceful way of handling this? Is there a way of > checking for this failure on the Pyramid side? > not without violating the WSGI standard. You can trap the exception in python but i have no idea of what will happen on the higher levels. Take in account that when a client timeout there is nothing you can do for it as teh connection is already closed -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
