When *we* generate SCRIPT_FILENAME, we simply use what r->filename is. On Sep 11, 2014, at 3:04 AM, Jan Kaluža <[email protected]> wrote:
> On 09/10/2014 07:17 PM, Jim Jagielski wrote: >> I know that PHP is current doing a LOT of fixes on >> hPHP-FPM... > > I've recently come to https://bugs.php.net/bug.php?id=65641 and was thinking > if we can do anything about it. > > Jan Kaluza > >> On Sep 10, 2014, at 12:00 PM, Martynas Bendorius <[email protected]> >> wrote: >> >>> Hello, >>> >>> http://httpd.apache.org/docs/current/mod/mod_proxy.html#handler breaks >>> PHP-FPM SCRIPT_FILENAME. It contains double "//" at the beginning of it >>> like: >>> SCRIPT_FILENAME: //home/admin/domains/testing.tld/public_html/test.php >>> >>> While it should be: >>> SCRIPT_FILENAME: /home/admin/domains/testing.tld/public_html/test.php >>> >>> Replacing "localhost/" to just "localhost" fixes the problem (removing / >>> from the end). >>> >>> I mean: >>> SetHandler "proxy:unix:/path/to/app.sock|fcgi://localhost" >>> >>> Instead of: >>> SetHandler "proxy:unix:/path/to/app.sock|fcgi://localhost/" >>> >>> Should it be considered a typo in Apache documentation or a bug in the way >>> PHP-FPM SAPI translates the path? >>> >>> Thank you! >>> >>> -- >>> Best regards, >>> Martynas Bendorius >>> >> >
