Certain Custom php.ini settings seem to be stripped before being saved to .conf file

Hello,

I've pasted the following values into the "Custom php.ini settings" field in ISPConfig 3:

Code:

display_startup_errors=On
display_errors=On
safe_mode=Off
register_globals=Off
magic_quotes_gpc=Off
memory_limit=512M
post_max_size=2048M
file_uploads=On
upload_max_filesize=2047M
log_errors=On
session.cookie_lifetime=0
session.gc_maxlifetime=2592000
max_execution_time=0
max_input_time=0

This is a local development environment, and I need these unusually large values for testing.

After making this change, and waiting for ISPConfig to commit the change to disk (in /etc/php5/fpm/pool.d/web1.conf in this case), I notice that several of the directives have been stripped out of the resultant values in web1.conf:

Code:

php_admin_flag[display_startup_errors] = On
php_admin_flag[display_errors] = On
php_admin_flag[safe_mode] = Off
php_admin_flag[register_globals] = Off
php_admin_flag[magic_quotes_gpc] = Off
php_admin_value[memory_limit] = 512M
php_admin_value[post_max_size] = 2048M
php_admin_flag[file_uploads] = On
php_admin_value[upload_max_filesize] = 2047M
php_admin_flag[log_errors] = On
php_admin_value[session.gc_maxlifetime] = 2592000

The following three are missing:

Code:

session.cookie_lifetime=0
max_execution_time=0
max_input_time=0

Is ISPConfig intentionally stripping these directives? If so, I assume that there is good reason for it, and if that rationale is documented somewhere, I would appreciate a link.

If PHP-FPM doesn't allow certain directives to be overridden in this way, is there documentation that lists which directives are subject to this limitation?

Thanks for any help!

 

Thanks for the reply, Till. This happens in ISPConfig 3.0.5.3.

 

Till, I went ahead and opened a ticket for this:

http://bugtracker.ispconfig.org/index.php?do=details&task_id=3366