|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
[2012-06-09 17:43 UTC] nospam at bigalex dot it
Description: ------------ Since PHP-FPM is the one taking care of the chroot, I think the problems related to inconsistent variables should be solved here. In fact, even if the environment is chrooted, the following variables still give the unchrooted content: $_SERVER["SCRIPT_FILENAME"] $_SERVER["PATH_TRANSLATED"] $_SERVER["DOCUMENT_ROOT"] I don't think this behaviour has to be solved by apache, nginx, lighttpd or any other web server, since the web server is not chrooted, instead it is connecting to PHP-FPM process through (tcp) sockets; for this reason I am working on a patch to fix this behaviour and in case the bug will be accepted, I will be happy to share the solution with you ;-) I've already looked for a solution or a bug request about it, and the bug #55322 is already about this problem; my analysis however is deeper than the other because the variables seems to be three and not just one. The proposed "fix" to symlink the real path into the chroot isn't clean, so I think this should be resolved here, inside php-fpm, and not with some weird workarounds. Test script: --------------- Inside a pool, I use the chroot feature, this way: chroot = /home/vhosts/h0001 expecting the scripts would be allowed to be executed with the chroot environment in mind, so the variables SCRIPT_FILENAME, PATH_TRANSLATED, DOCUMENT_ROOT should be changed accordingly before the script being executed (so their value should be the one into the chroot environment). Expected result: ---------------- As an example, the value $_SERVER["PATH_TRANSLATED"] should be /home/domains/test.com/phpinfo.php Actual result: -------------- As an example, the value $_SERVER["PATH_TRANSLATED"] is /home/vhosts/h0001/home/domains/test.com/phpinfo.php PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sun Oct 26 06:00:02 2025 UTC |
From my point of view, I'd rather prefer to configure this on the web server side (if it's not possible with apache then switch to something else -- aka nginx for exemple. If apache does not suit well with fastcgi customizations, then ask apache guys :p) more seriously, I can understand the need. I'll try to look at this to dynamicaly adapt fastcgi variables from the chroot env. The following algorithm should work: for variable in all_fastcgi_variables; do if ($_SERVER[$var] =~ /^$chroot(.*)$/); then $_SERVER[$var] = $1; fi done or somehting more restrictive: for var in "DOCUMENT_ROOT" "SCRIPT_FILENAME" "PATH_TRANSLATED"]; do if ($_SERVER[$var] =~ /^$chroot(.*)$/); then $_SERVER[$var] = $1; fi end