1. This is the general setup i have at the moment: http://dpaste.com/hold/362090/ plain/
basically nginx frontend dynamically invoking uWSGI based on provided SCRIPT_NAME and host, and uWSGI handles python scripts. for GET everything works as expected, however for POST request there are certain anomalities: $ curl -d "" http://pkolla:88/report/ p report $ curl -d "anything" http://pkolla:88/report/ $ if anything is passed as post-data the serverside does not return anything to client (local, remote, wget, browser or curl - no difference) more details available here: http://dpaste.com/362107/plain/ the issues seems to be somewhere on way back from uWSGI to nginx, nginx claims that conneciton was dropped but based on packet sniffing with tcpdump/tshark i can see that uWSGI seems to work very similar in both cases, with or without post-data detailed traffic dumps no post data: http://dpaste.com/362049/plain/ and with post data: http://dpaste.com/362051/plain/ 2. Probably irrelevant to first issue but just in case: despite launching uWSGI with --no-default-app param i still see in logs: setting default application to 0 And in case if uWSGI gets request which is not possible to handle because of missing modules (due to domain and hence document root & python path not physically existing), the request is being passed to whichever app was handling same module (looks like script_name seems to matter here) on some other domain. Yet in case if there were no default application set - it returns an error as expected. Will appreciate any help, thanks in advance _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
