Changes between Version 2 and Version 3 of Ticket #1223, comment 2


Ignore:
Timestamp:
03/21/17 15:54:00 (8 years ago)
Author:
Kevin Fischer

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1223, comment 2

    v2 v3  
    1 You seem to misunderstand the problem here. It doesn't matter that it's a PHP script that is being executed; it could be any file. The problem is the combination of a try_files fallback in combination with resolving the error pages, which did not exist. nginx will ignore the deny all; statement when resolving for the error pages, thus falling back to index.php in my example, as configured by try_files. But again: this could be any file, and that file would be delivered with a 404 response code, despite nginx being instructed to deny access.
     1You seem to misunderstand the problem here. It doesn't matter that it's a PHP script that is being executed; it could be any file. The problem is the combination of a try_files fallback in combination with resolving the error pages, which did not exist. nginx will fall back to index.php in my example, as configured by try_files. But again: this could be any file, and that file would be delivered with a 404 response code, despite nginx being instructed to deny access.
    22
    33A request timeline (which might not be correct 100%, as I don't know the nginx source code - this is just what I figured out from debugging this):