Closed Jaymon closed 9 years ago
I think this has always been happening, it's just the new lazy loading code that came about from the 1.0 release brought it into our logging system that alerted us to this error instead of letting it fail silently and restart the process.
Possibly related: http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/5386 http://lists.unbit.it/pipermail/uwsgi/2014-May/007330.html http://stackoverflow.com/questions/3823280/ioerror-request-data-read-error https://github.com/unbit/uwsgi/issues/363
These now will trigger a 408 call error when encountered
I think this has always been happening, it's just the new lazy loading code that came about from the 1.0 release brought it into our logging system that alerted us to this error instead of letting it fail silently and restart the process.
Possibly related: http://comments.gmane.org/gmane.comp.python.wsgi.uwsgi.general/5386 http://lists.unbit.it/pipermail/uwsgi/2014-May/007330.html http://stackoverflow.com/questions/3823280/ioerror-request-data-read-error https://github.com/unbit/uwsgi/issues/363