Home » Php » php – Wrong SCRIPT_FILENAME & PHP_SELF in Apache 2.4.26

php – Wrong SCRIPT_FILENAME & PHP_SELF in Apache 2.4.26

Posted by: admin July 12, 2020 Leave a comment

Questions:

With Apache 2.4.26 using php-fpm 7.1.6, $_SERVER['SCRIPT_FILENAME'] (and $_SERVER['PHP_SELF']) is incorrect on a folder:

Apache 2.4.26:

/index.php

Apache 2.4.25:

/myfolder/index.php

What is wrong?

How to&Answers:

I fixed it in apache config with this new config directive :

ProxyFCGIBackendType GENERIC

In global configuration before the SetHandler directive. Default is FPM, but it’s not correct with some php-fpm configuration (SetHandler and socket).

With this bug all $_SERVER['SCRIPT_FILENAME'] and $_SERVER['PHP_SELF'] Apache vars ($_SERVER) (injected from php-fpm) are wrong, they don’t have the path!

ProxyFCGIBackendType is default to FPM but it’s wrong for many configuration.
Apache httpd should add GENERIC as default to don’t break websites.

See: https://httpd.apache.org/docs/2.4/en/mod/mod_proxy_fcgi.html#proxyfcgibackendtype

Answer:

(This would be better as a comment, but I’m under the minimum rep.)

Like neoteknic points out in their answer, using the GENERIC backend type will revert you to 2.4.25 behavior while we get this bug worked out.

Note, however, that the 2.4.25 behavior breaks some other people too and is not a panacea. If you’re in a bind, the new ProxyFCGISetEnvIf directive can give you direct control over FCGI envvars, and it accepts httpd expression syntax for some pretty complex manipulations, if you need them. This only helps if you understand what those envvars are supposed to be, but it’s another option.