List of php.ini sections

Questa lista include le sezioni php.ini che possono essere utilizzate per configurare un'installazione PHP a seconda dell'Host virtuale o del Path. Queste sezioni sono opzionali.

Queste sezioni non modificano direttamente il comportamento di PHP. Sono usate per raggruppare le altre direttive php.ini in modo da farle agire risptto ad un determinato host o percorso.

Queste sezioni sono usate solo in modalità CGI/FastCGI e non possono impostare direttive extension e zend_extension.

Sections
Nome Modificabile Storico dei cambiamenti
[HOST=] PHP_INI_SYSTEM Aggiunto in PHP 5.3.0.
[PATH=] PHP_INI_SYSTEM Aggiunto in PHP 5.3.0.

Breve descrizione dei parametri di configurazione.

[HOST=<host>]

Questa sezione permette di definire un gruppo di direttive php.ini che verranno applicate all'host specificato.

Example #1 Attivare la visualizzazione completa degli errori per il dominio dev.

[HOST=dev.site.com]
error_reporting = E_ALL
display_errors = On

[PATH=<path>]

Questa sezione permette di definire un gruppo di direttive php.ini che verranno applicate quando un script verrà eseguito a partire dal percorso specificato.

Example #2 Aggiungere uno script di sicurezza per le aree protette

[PATH=/home/site/public/secure]
auto_prepend_file=security.php

add a note add a note

User Contributed Notes 6 notes

up
4
leo
2 years ago
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".
up
2
z dot himdi at bita dot nl
2 years ago
On Windows IIS 7 server I noticed that [PATH=] was not listened to. [HOST=] however worked.
up
1
robert dot johnson at icap dot com
4 years ago
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.
up
0
crash at lubyte dot de
3 years ago
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.
up
0
public at grik dot net
4 years ago
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).
up
-1
stickman
3 years ago
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).
To Top