Maxim, Thank you for your reply.
On Thu, Jan 9, 2014 at 10:03 AM, Maxim Dounin <[email protected]> wrote: > [snip] > > If you are able to connect to localhost:9090 with your browser, > you are likely using native HTTP support in your uWSGI server. > Yes, I am starting the uwsgi process like this, using the --http flag: uwsgi --http :9090 --wsgi-file foobar.py --master --processes 4 --threads 2 > The "uwsgi_pass" directive assumes uwsgi protocol though, which is > different. > > You should either reconfigure uWSGI server to work via uwsgi, or > Ah, I see, I should use the --socket option instead, like this: uwsgi --socket 127.0.0.1:9090 --wsgi-file foobar.py --master --processes 4 --threads 2 Thank you for clarifying that; it *is* in the uwsgi docs I quoted earlier, but it is a subtle point under the "quickstart" section, and I had missed it. > instruct nginx to talk via HTTP (i.e., use "proxy_pass" instead of > "uwsgi_pass"). > I see: I could use "proxy_pass" and keep --http when I start uwsgi. Thank you, that was very helpful!
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
