Hi Thijs Le sam 20 sep 12:49, Thijs Kinkhorst a écrit : > > Thank you for your report. I looked into this, but could confirm that setting > LoginCookieValidity in /etc/phpmyadmin/config.inc.php does indeed cause that > information to end up in the appropriate function. > > Are you sure that your PHP configuration doesn't clean up the session before > the timeout happens? Check the session session.gc_maxlifetime parameter > in /etc/php5/*/php.ini, Could you check for me what value it has and if > raising the value (and restarting Apache) has any effect?
Thank you for taking time in investigating this. That's right, my global php.ini sets this parameter to 1800. But phpMyAdmin doesn't have to follow this default parameter. IIRC, it can use ini_set() to locally change the value of session.gc_maxlifetime. If it doesn't, it should at least mention this in its user documentation. If phpMyAdmin uses the default session parameters (lifetime, path, handler...) then any php application running on the same server can delete its sessions anytime. I still think it's a bug, or at least a lacking feature. Thanks again -- François -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
