Am I wrong that uwsgi_params in nginx needs to have these in order for https to be properly signalled to the applications:uwsgi_param UWSGI_SCHEME $scheme; uwsgi_param HTTPS $https if_not_empty; The second one is needed for CGI at least, maybe for PHP too, haven't tested it yet.
It depends on the app/technology used, it has been already proposed to have them specified by default in nginx configs but honenslty i am not sure if it would break some old apps in any way. By the way both PHP and CGI requires HTTPS to be set for correct https handling.
scgi_params in nginx already has the second by default. How can these options break an app? If anything it'll unbreak them. -- дамјан _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
