Thanks a lot Roberto, this is exactly what I'm looking for. Just out of curiosity, if the body has to be read anyway, why not read it in uWSGI by default? And then the application can choose to use the body or not, but no error will be reported even if the application forget to read the body (or sometimes for certain request the application just don't care the "body").
I had this issue when I was trying to do some "insane" operations, which is to give a "body" to a "GET" request. This will not happen in a sane application such as a web browser, but it could happen in an HTTP programming library, where you never know what kind of "insane" operations the client could ever make, and in all my request handler, I have to read body the very first thing to do. Is it because of performance considerations or something else? > All is described here: > > http://uwsgi-docs.readthedocs.org/en/latest/ThingsToKnow.html > > Basically, if there is a body you have to read it. If you do not want to > bother, just use post-buffering that will read the body for you. > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
