> I forgot to mention, someone said - "That happens because you do not read > the whole request body in your app." > > I do not believe this is true.. we are handling a multipart form and the > image is complete > > uwsgi fails silently without any error, but nginx seems to detect the > socket issue. >
It is exactly the behaviour when your app does not read the whole body, and the reason why post-buffering exists :) The problem is not in uWSGI but in the way nginx manages events (and more in deep how sockets work). post-buffering simply automatically read the http body before calling the WSGI application. Tiny chunks are written in memory, while bigger are saved to disk using temporary unlinked files. If you manage to ensure your app will read POST data when there is something to read, post-buffering is useless. In the next few days i will check if we can have a custom tmpfile implementation to allow the user to configure its behaviour at a lower level. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
