Bug #62279 [Ana->Opn]: PHP-FPM chroot never-solved problems (extends #55322)

From: Date: Thu, 02 Feb 2017 12:06:16 +0000
Subject: Bug #62279 [Ana->Opn]: PHP-FPM chroot never-solved problems (extends #55322)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-207116@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=62279&edit=1 ID: 62279 Updated by: requinix@php.net Reported by: nospam at bigalex dot it Summary: PHP-FPM chroot never-solved problems (extends #55322) -Status: Analyzed +Status: Open Type: Bug Package: FPM related Operating System: Irrelevant PHP Version: Any -Assigned To: fat +Assigned To: Block user comment: N Private report: N Previous Comments: ------------------------------------------------------------------------ [2017-02-02 11:00:15] ghosh at pw6 dot de #69090 has nothing to do with this bug. This bug still exists in 7.1. ------------------------------------------------------------------------ [2016-11-29 15:15:38] sjon at hortensius dot net This was partially fixed in #69090 ------------------------------------------------------------------------ [2013-10-26 16:16:45] admin at franceserv dot fr More 1 year (15 month) after the last comment, i have the same problem and i don't think this bug is solved. Everybody have migrate to Nginx instead Apache ? I can't do it because my hosted need to use .htaccess for Apache. Thanks so much for your reply ... ------------------------------------------------------------------------ [2012-07-19 00:44:43] graham at wyenet dot net Moving to nginx would be lovely, but on many low cost virtual hosting scenarios where a dedicated server would be totally overkill, many end users are still heavily using .htaccess files (Yes I know the arguments against.. performance, excessive stats, too many reads etc etc...) Take just about any off the shelf, wordpress, drupal, magento etc, and it comes ready to roll on Apache, and fully loaded with .htaccess files. The argument against changing it from the Apache side of things, is that Apache has simply followed the standards for FastCGI, and that since its PHP-FPM that has created the jail, Apache doesnt even need to know that its happened. Your proposed solution to the problem should sort it out though, I assume it would also avoid the "not found" problem when fix.cgi_pathinfo is set to 1. If you have a patch, Im quite happy to try it on one of my systems to check it corrects the problem in various "off the shelf" configurations, and if any problems still occur, im happy to share the config file. PHP-FPM works brilliantly with Apache / FastCGI with sockets.. but would be nice to get the chroot working without resorting to symlink workarounds etc. ------------------------------------------------------------------------ [2012-07-04 17:08:10] fat@php.net I used pseudo bash syntax but it'll be implemanted inside fpm (with C code) ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=62279 -- Edit this bug report at https://bugs.php.net/bug.php?id=62279&edit=1

« previous php.bugs (#207116) next »