[prev in list] [next in list] [prev in thread] [next in thread]
List: nginx
Subject: Re: Problem with uWSGI and PATH_INFO
From: Etienne Robillard <tkadm30 () yandex ! com>
Date: 2017-07-29 10:09:01
Message-ID: e28a0a0d-ce3b-9a40-5f61-1c5ca2ab6436 () yandex ! com
[Download RAW message or body]
Hi Francis,
Le 2017-07-28 à 03:17, Francis Daly a écrit :
>
> What I meant there was that you could possibly use fastcgi_split_path_info
> to define how you want your $request_uri to be split into parts for your
> SCRIPT_NAME and PATH_INFO as uwsgi_param values.
>
> So your eventual config could include
>
> uwsgi_param SCRIPT_NAME $fastcgi_script_name;
> uwsgi_param PATH_INFO $fastcgi_path_info;
>
> after you have defined the first directive appropriately.
>
> It all comes down to: for one specific http request, what values do
> you want SCRIPT_NAME and PATH_INFO to have when they are sent to the
> uwsgi upstream?
>
>
I'll try your workaround. I want nginx to manage SCRIPT_NAME and
PATH_INFO in FastCGI mode, and uWSGI to act as a FastCGI handler.
Etienne
--
Etienne Robillard
tkadm30@yandex.com
http://www.isotopesoftware.ca/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic