-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP configuration #26
Comments
These settings do not work if only in the apache configuration.
Have these been tried in the script itself, rather than Apache? (Both ought to work of course.) |
Yes, just now, (if I get what you mean by 'script`), but with the same negative outcome. I tried removing the ini_set ('session.gc_maxlifetime', 2000);
ini_set ('session.cookie_lifetime', 1600);
ini_set ('zend.assertions', 0); and
and via another route: I also tried with those values as strings rather than int. So, this is the same result as has been previously tried via the apache configuation. |
That correctly shows that the local value, i.e. the one actually used by the application, is in use. I can't see what the problem is. (The master value is just for information, namely saying what the system value is, but it's rarely interesting.) |
Yes theoretically as I understand it, but in practice for these directives this local value is being ignored. |
Difficult directives
Despite being listed as PHP_INI_ALL the following directives are not effectively assigned to values applied from the Apache configuration:
The assigned values are respected when included in the
php.ini
system, as has been tried for example in 9998f11.The
zend.assertions
directive controls how PHP is compiled which might be why it has to be set in the php.ini system, and the qualificationwith restrictions
is a hint to that.phpinfo()
Despite looking at this many times over the last decade I have never gotten to the bottom of why the other two settings cannot be set reliably from the Apache configuration. E.g. when set in the either a
virtualhost
configuration or the one of the higher levelconf-enabled
files to 86400,phpinfo()
lists them as:(1440 = 24 minutes, 86400 = 24 hours)
but the setting in force appears to be the master value as about 24 minutes later the site requests a login. (This wait also makes it a pain to test / debug.)
I think it might be something to do with the server wide nature of these settings - e.g. the garbage collection lifetime presumably applies to the whole of php as perhaps hinted at by the note attached to this documentation for the session.gc_maxlifetime directive.
Consequence
Until this matter can be resolved then changing these values from their defaults requires edits in the php.ini system files.
The text was updated successfully, but these errors were encountered: