> Hi all, > > Le 2017-07-27 à 11:25, Francis Daly a écrit : >> On Thu, Jul 27, 2017 at 07:45:28AM -0400, Etienne Robillard wrote: >> >> Hi there, >> >>> I'm not sure I understand the logic of this. Can someone please >>> explain why the variable PATH_INFO is set to $document_uri in >>> uwsgi_params? >> My guess (without knowing the history): >> >> The uwsgi_params values are an example of what can be done. The >> combination of SCRIPT_NAME and PATH_INFO in that file is consistent, and >> is valid in some cases (that is, cases where the application corresponds >> to the "root" of the server). > Actually my problem is that SCRIPT_NAME is not defined in uwsgi_params. > SCRIPT_NAME is a mandatory environment variable as per HTTP/1.1 spec. >> >> No-one has reported that there is a problem and provided a fix. > That's a major issue. A standard WSGI application should be able to use > a uWSGI upstream server within the "/" location block without the need > to define any "mountpoints". >
Then just add uwsgi_param SCRIPT_NAME ""; in uwsgi_params :) -- Roberto De Ioris http://unbit.com _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
