PHP運作于Apache 子產品方式
當使用 PHP 作為 Apache 子產品時，也可以用 Apache 的配置檔案(例如 httpd.conf)和 .htaccess 檔案中的指令來修改 PHP 的配置設定。需要有“AllowOverride Options”或“AllowOverride All”權限才可以。
有幾個 Apache 指令可以使使用者在 Apache 配置檔案内部修改 PHP 的配置。哪些指令屬于 PHP_INI_ALL，PHP_INI_PERDIR 或 PHP_INI_SYSTEM 中的哪一個，請參考附錄中的 php.ini 配置選項清單。
php_value name value
設定指定的值。隻能用于 PHP_INI_ALL 或 PHP_INI_PERDIR 類型的指令。要清除先前設定的值，把 value 設為 none。
Note: 不要用 php_value 設定布爾值。應該用 php_flag(見下面)。
php_flag name on|off
用來設定布爾值的配置指令。僅能用于 PHP_INI_ALL 和 PHP_INI_PERDIR 類型的指令。
php_admin_value name value
設定指定的指令的值。不能用于 .htaccess 檔案。任何用 php_admin_value 設定的指令都不能被 .htaccess 或 virtualhost 中的指令覆寫。要清除先前設定的值，把 value 設為 none。
php_admin_flag name on|off
用來設定布爾值的配置指令。不能用于 .htaccess 檔案。任何用 php_admin_flag 設定的指令都不能被 .htaccess 或 virtualhost 中的.指令覆寫。
Example #1 Apache 配置例子
php_value include_path ".:/usr/local/lib/php"
php_admin_flag engine on
php_value include_path ".:/usr/local/lib/php"
php_admin_flag engine on
Caution
PHP 常量不存在于 PHP 之外。例如在 httpd.conf 中不能使用 PHP 常量如 E_ALL 或 E_NOTICE 來設定 error_reporting 指令，因為其無意義，實際等于 0。應該用相應的掩碼值來替代。這些常量可以在 php.ini 中使用。
通過 Windows 系統資料庫修改 PHP 配置
在 Windows 下運作 PHP 時，可以用 Windows 系統資料庫以目錄為機關來修改配置。配置值存放于系統資料庫項 HKLM\SOFTWARE\PHP\Per Directory Values 下面，子項對應于路徑名。例如對于目錄 c:\inetpub\wwwroot 的配置值會存放于 HKLM\SOFTWARE\PHP\Per Directory Values\c\inetpub\wwwroot 項下面。其中的設定對于任何位于此目錄及其任何子目錄的腳本都有效。項中的值的名稱是 PHP 配置指令的名字，值的資料是字元串格式的指令值。值中的 PHP 常量不被解析。不過隻有可修改範圍是 PHP_INI_USER 的配置值可以用此方法設定，PHP_INI_PERDIR 的值就不行。
其它接口下的 PHP
無論怎樣運作 PHP，都可以在腳本中通過 ini_set() 而在運作時修改某個值。更多資訊見手冊中 ini_set() 的頁面。
如果對自己系統中的配置設定及其目前值的完整清單感興趣，可以運作 phpinfo() 函數并檢視其結果的頁面。也可以在運作時用 ini_get() 或 get_cfg_var() 取得個别配置指令的值。
add a note add a note
User Contributed Notes 13 notes
up
down
3 Anteaus ?2 years ago
One of the most serious problems here is that it is hard to determine programmatically which of three or more possible configuration methods (php.ini, .user.ini, .htaccess) should be used on any given hosting company's server.
The worst outcome is if an install.php routine attempts to set .htaccess directives on a cgi-mode server, in which case the outcome is usually a '500' crash. Once in that situation the php installation routine cannot be rerun to correct the problem, so you effectively have a hosting lockout situation which can only be corrected by manual intervention.
up
down
-2 contrees.du.reve at gmail dot com ?9 years ago
Being able to put php directives in httpd.conf and have them work on a per-directory or per-vitual host basis is just great. Now there's another aspect which might be worth being aware of:
A php.ini directive put into your apache conf file applies to php when it runs as an apache module (i.e. in a web page), but NOT when it runs as CLI (command-line interface).
Such feature that might be unwanted by an unhappy few, but I guess most will find it useful. As far as I'm concerned, I'm really happy that I can use open_basedir in my httpd.conf file, and it restricts the access of web users and sub-admins of my domain, but it does NOT restrict my own command-line php scripts...
up
down
-3 nick at vistaworks dot net ?4 years ago
On Windows, as the documentation above states, you cannot set max_upload_filesize and post_max_size in the registry, because they are PHP_INI_PERDIR.
Confusingly, however, is the fact that phpinfo() will show your changes if you do add those to the regsitry, as if they were taking effect. However, the upload size is *not* changed, regardless of what phpinfo() reports.
I believe the reading of registry values and override happen 'too late' in the request processing, ie, after the file has already been uploaded and rejected.
In a perfect world, phpinfo() would recognize this and not report the overridden values, which is very confusing.
up
down
-4 Woody/mC ?9 years ago
@ pgl: As the documentation says:
"To clear a previously set value use none as the value."
Works fine for me.
up
down
-6 user at NOSPAM dot example dot com ?5 years ago
PHP Constants will work with php_value; for example: