Support for mod gzip
You may use the gzip output for your PHP scripts though.
Because we use suPHP to parse php files, you have the option of using a custom php.ini file.
Your account can have multiple php.ini files on your account in different folders so you can customize the php processing in different folders should your script require it. A php.ini file will not inherit down into subfolders, however, you can create a .htaccess file in the same folder as the php.ini file and place the following code into it:
where "username" is your cPanel username. This will cause the php.ini file to affect all subfolders, unless a php.ini file is in a subfolder, at which point the php.ini in the subfolder takes precedence.
In php.ini, you will need to use the actual php.ini syntax instead of the php_value or php_flag syntax you would normally use in .htaccess (Which should not be used at all):
setting_name = setting_value
So, this means if you move the settings from .htaccess to php.ini, you must convert the format. Let's say you have the following line in your .htaccess file:
php_value register_globals 0
the corresponding php.ini format is as follows:
register_globals = Off
Notice how the value 0 becomes Off and 1 becomes On. Now if your php_value has quotes like the following, for example:
php_value include_path ".:/home/user/lib"
The corresponding php.ini format is:
include_path = ".:/home/user/lib"
and so on. You should only use the settings you need to change in your php.ini.
For the PHP settings you do not have in your php.ini file, PHP will use our default configurations.
Want to read this in another language?