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).
No-one has reported that there is a problem and provided a fix.
In general, only the administrator knows what SCRIPT_NAME and PATH_INFO
values are appropriate in any one case, so that's the person who should
configure the two to match their particular case.
In the case of fastcgi, someone saw a possibly-similar issue and went
to the bother of adding a fastcgi_split_path_info directives which splits
the request uri string into two variables.
Perhaps it would be useful for something similar to exist for uwsgi? The
fact that it does not exist already suggests that no-one has enough of
a need, to arrange that it be added.
I guess that a server-level "if" could "set" two variables that could be
used to populate SCRIPT_NAME and PATH_INFO, until a uwsgi_split_path_info
directive is introduced. And that might be enough to avoid the need for
a dedicated directive.
(Actually: perhaps fastcgi_split_path_info can be used directly, even
in a location{} which does not do fastcgi_pass? It should be easy enough
to test whether that can work.)
The hard part is usually deciding what exactly is wanted. After that,
the implementation can be considered.
Good luck with it,
f
--
Francis Daly fran...@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
