No - the last argument to try_files is different to the other arguments.
If this last argument is used, you get an internal redirect to the url
/grant/index.php?$args, and the appropriate location{} to handle that
request is chosen from scratch.
Which shows exactly what you see, which is not w
Thanks for the response.
> I suggest using a named location for handling the "not there" fallback
> -- either as the final argument to try_files, or perhaps as "error_page
> 404 = @fallback".
>
> Then
>
> location @fallback {
>fastcgi_param SCRIPT_FILENAME /apps/grant/index.php;
>includ
Is this the issue I might be experiencing when I try to use the alias directive?
https://trac.nginx.org/nginx/ticket/97
> On Sep 7, 2015, at 11:23 AM, Kristofer Pettijohn
> wrote:
>
> I am having a difficult time finding a solution for this.
>
> I have PHP applications that
I am having a difficult time finding a solution for this.
I have PHP applications that may be referenced to from several websites, either
from root locations or sub locations.
For example:
server {
server_name domain.com;
location / {
... unrelated stuff ...
}
location /grant {
root /a
Hello,
I am using nginx as a reverse proxy to cache content for an application.
Requests to the application are expensive, so I would like to set up caching so
that if the file exists in nginx, it won't even bother querying the backend
server.
I can't seem to figure out what I am missing.
