> Ok, one more post: I've done a bit more troubleshooting and I've found > that when I put uWSGI in http mode and stop Nginx from running, I get > the correct response while accessing the app through facebook. So, it > looks like the problem is Nginx or uWSGI closing the connection before > the response is read. However, the question that still remains is why > is it doing this? Any ideas?
check if there is some "uwsgi_intercept_*" options in nginx enabled or some "uwsgi_next" triggering a fallback in nginx itself. Take in account that uWSGI makes no difference between normal requests or nginx internal redirect. Maybe the 503 is genrated by a nginx internal redirect. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
