> Dear uwsgi users and developers, > I'm having a nginx (1.1.19) + uwsgi (1.0.3) set up. > In my python WSGI application, if a request wth a non-empty HTTP body > is received > but the python WSGI application is not really using it, nginx will > report error 500. > But from the uwsgi log, the request can be seen properly generated. > As long as I consume the HTTP request "body" the first thing in my > WSGI application, > everything will then work fine. > > I'm not sure if this is an nginx issue or an uwsgi issue, but google > around shows that > Apache server has a similar behavior and apache people think the behavior > is OK. > > Anyone can give me some hints? > > Thanks a lot. > Yanghao > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
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
