Re: startup sequencing issue with php_admin_value disable_functions?
| From: | Zeev Suraski | Date: | Wed, 24 Oct 2001 15:53:12 +0000 |
| Subject: | Re: startup sequencing issue with php_admin_value disable_functions? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-68961@lists.php.net to get a copy of this message | ||
At 17:44 24-10-01, Rasmus Lerdorf wrote:
At 09:30 24-10-01, Rasmus Lerdorf wrote:Yes they can. The way PHP works is that you have different settings for different vhosts, or different directories for that matter, each request will first set PHP up to the right settings, and then perform the request... There aren't copies of the data structures (e.g., the function table) for different vhosts. If we were to make it work, we'd have to implement a mechanism that knows how to disable functions and re-enable them when the request terminates, so that the next request is not affected. It's not impossible, but this code currently does not exist. Zeevphp.ini.At 07:55 24-10-01, Rasmus Lerdorf wrote:php_admin_value disable_functions does not work. Works fine fromLook at the code... It's really designed to be a one-time thing, rather than something that can be easily turned on/off - if it was supported on a per-virtual-host basis. It can be implemented, but it would require quite a bit of coding, as this functionality is simply not there right now. I did look at the code and I still don't understand. It's not like httpd.conf directives can be run multiple times under normal circumstances.It's not supposed to work, it can only work from php.ini.Why?