Try_files does not hit PHP ( NginX configuration)

Question

Below is my nginx.conf.

In case of non existing files /index.php is served fine.

But when my URL is /foo/bar => /foo/bar/index.php is served as PHP source code via download.

Any ideas?

try_files $uri $uri/ $uri/index.php /index.php;

location ~ \.php$ { 
    fastcgi_pass 127.0.0.1:9000;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
}

:-) Sure it even serves the last option /index.php if I put non existing URL. — Benjamin Harel
– Benjamin Harel, Commented Aug 23, 2012 at 12:49
I have the same problem. If I hit a url that maps to a non-existent file, it correctly executes index.php. However, if I place a new php file and attempt to hit that file directly, I get its source code — D-Rock
– D-Rock, Commented Aug 23, 2012 at 12:50
Hmm the only difference I can see between mine and yours is mine isn't inside a location. try_files $uri $uri/ /index.php?$args; — Gabriel Baker
– Gabriel Baker, Commented Aug 23, 2012 at 12:54
in your example above, what heppens when you try /foo/bar/index.php directly? — Gabriel Baker
– Gabriel Baker, Commented Aug 23, 2012 at 14:07

Benjamin Harel · Accepted Answer · 2012-08-23 15:08:32Z

3

Solution was to add index index.php

    index index.php

    try_files $uri $uri/ $uri/index.php /index.php;

    location ~ \.php$ { 
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

answered Aug 23, 2012 at 15:08

Benjamin Harel

2,9463 gold badges27 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Mahmoud Al-Qudsi Over a year ago

Actually, the solution is to use a named location as the final parameter to try_files. The problem is that an internal redirect (i.e. an attempt to check if any other regexes such as your PHP handling regex) is only issued for the final fallback parameter. In the configuration in your question, the request for /index.php did not even try to match the regex. The reason your answer works is because index anything will issue an internal redirect if anything is accessed, causing the actual PHP regex to match.

Pete Over a year ago

@MahmoudAl-Qudsi could you post an answer showing how to use a named location

amitchhajer · Accepted Answer · 2012-08-23 13:29:29Z

1

My config

index index.html index.htm index.php;
location ~ \.php$ {
        fastcgi_pass unix:/tmp/php-fpm.sock;
        include fastcgi_params;
      }

reload nginx and fastcgi both

answered Aug 23, 2012 at 13:29

amitchhajer

13k6 gold badges43 silver badges54 bronze badges

1 Comment

Benjamin Harel Over a year ago

I'm talking about try_files. Actually I need more patterns to use with try_files like drupal and passenger. But adding index index.php solved this. Thanks.

Ville · Accepted Answer · 2014-09-26 17:38:26Z

0

I also had this same issue. When I had the following in the PHP context (location ~ ^(.+\.php)(.*)$ { ...):

try_files $fastcgi_script_name =404;

.. it always returned 404. Finally I read the try_files docs, where it says:

The path to a file is constructed from the file parameter according to the root and alias directives.

I had only defined alias for each location block (and none in the PHP-FPM block, of course), but didn't have an overall root set anywhere, so NGiNX didn't know where to look for a file. Once I set root for the server block, it started working.

answered Sep 26, 2014 at 17:38

Ville

4,3662 gold badges40 silver badges40 bronze badges

Collectives™ on Stack Overflow

Try_files does not hit PHP ( NginX configuration)

3 Answers 3

2 Comments

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related