[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nginx
Subject:    Re: Problem with uWSGI and PATH_INFO
From:       Francis Daly <francis () daoine ! org>
Date:       2017-08-08 18:11:41
Message-ID: 20170808181141.GE365 () daoine ! org
[Download RAW message or body]

On Sun, Aug 06, 2017 at 12:28:11PM +0200, Roberto De Ioris wrote:
> > On Sat, Aug 05, 2017 at 11:47:24AM -0400, Etienne Robillard wrote:

Hi there,

> nginx is not able to correctly split PATH_INFO accordingly to SCRIPT_NAME

That is correct.

It is similarly correct that nginx is not able to know where your uwsgi
server is listening.

> (and technically it should not do it as uwsgi is a transport only protocol
> and the server could make any kind of assumptions about variables).

The administrator should know what variable values the uwsgi server will
make use of, and where the uwsgi server is listening.

The administrator can configure nginx to match whatever those
site-specific requirements are.

(And one possible way to do that, is for nginx to always set PATH_INFO
= the original request, and let the uwsgi server use that in any way
it likes.)

	f
-- 
Francis Daly        francis@daoine.org
_______________________________________________
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]