On Windows IIS 7 server I noticed that [PATH=] was not listened to. [HOST=] however worked.
This list includes the php.ini sections you can set to configure your PHP setup on a per Host or Path basis. These sections are optional.
These sections don't directly affect PHP. They are used to group other php.ini directives together and to get them to act upon a particular host or on a particular path.
These sections are used only in CGI/FastCGI mode and they can not set extension and zend_extension directives.
| 名字 | 可修改范围 | 更新日志 |
|---|---|---|
| [HOST=] | PHP_INI_SYSTEM | 在 PHP 5.3.0 时增加。 |
| [PATH=] | PHP_INI_SYSTEM | 在 PHP 5.3.0 时增加。 |
这是配置指令的简短说明。
[HOST=<host>]
This section allows you to define a set of php.ini directives that will take effect on the named host.
Example #1 Activate full on-screen error reporting for dev. domain
[HOST=dev.site.com] error_reporting = E_ALL display_errors = On
[PATH=<path>]
This section allows you to define a set of php.ini directives that will take effect when a script runs from the named path.
Example #2 Add security script for protected areas
[PATH=/home/site/public/secure] auto_prepend_file=security.php
On Windows IIS 7 server I noticed that [PATH=] was not listened to. [HOST=] however worked.
Just developed the probably first php.ini hack to add commands which will only be parsed before PHP 5.3 when using mod_php.
<?php
# Disable eAccelerator by default
eaccelerator.enable = 0
# Now, to prevent incompatibilities with Zend Optimizer+, we
# want to enable eAccelerator only in PHP 5.2 or lower.
[HOST=*]
eaccelerator.enable = 1
?>
What is happening here? In PHP 5.3, php.ini sections to set up PHP on a per host basis have been introduced:
http://www.php.net/manual/en/ini.sections.php
These sections only work in CGI/FastCGI mode, however there still seems to be a difference in how the php.ini file is parsed in PHP 5.2 and PHP 5.3 when using mod_php: PHP 5.3 ignores everything below the line [HOST=*], whereas PHP 5.2 does not.
In the above example, PHP 5.3 only reads "eaccelerator.enable = 0" and then stops at the invalid command [HOST=*]. However, PHP 5.2 seems to ignore the invalid command and parses the whole configuration file, ending up with "eaccelerator.enable = 1".
This doesn't seem to work with php-fpm.
The values defined under PATH or HOST will become the new master value for all the processes (as if they were redefined).
If you have a system which uses separated PHP inis for loading extensions (Debian, Fedora and most other distributions do so), [PATH=] or [HOST=] will prevent loading extensions defined in those ini files (extension= and zend_extension=).
I had some headache, when I added a hosts.ini to /etc/php5/cgi/conf.d (Debians default), where I wanted to define some defaults for a host name. The manual says extension= and zend_extension= aren't allowed in [HOST=] and [PATH=] (see above). I figured out that you can easily fix that with adding [PHP] after your definitions.
For example hosts.ini:
[HOST=dev.example.com]
display_errors = on
[PHP]
this will change the section back to [PHP] where extension= and zend_extension= is allowed.
Adding PATH= applies only to the named path and does not include sub-directories, you have to add a PATH= value for each sub-directory.
Also some settings have no effect even though phpinfo recognises and displays the per-folder value as the 'local' value, and the default as the 'master' value.
'fastcgi.impersonate' always uses the master setting.
In [HOST=...] one should use only the 1st server name from the list of server names.
I.E. if you have
server_name example.com, example2.com;
and will use www.example.com in a browser,
use [HOST=example.com] in php.ini for both addresses.
PHP looks not at the HOST request header (as I expected), but at the SERVER_NAME parameter (which by default is the 1st from the list of names, no matter what the HOST is).