Bug #15644 Updated: Wrong behaviour session.gc_maxlifetime

ID: 15644 Updated by: php-bugs@lists.php.net Reported By: ivo@ibuildings.nl -Status: Feedback +Status: No Feedback Bug Type: Session related Operating System: Redhat Linux PHP Version: 4.1.1 New Comment: No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: ------------------------------------------------------------------------ [2002-02-21 05:32:12] yohgaki@php.net I need to take a look at code... But before I do that, could you verify if this problem exists in CVS version? http://snaps.php.net/ ------------------------------------------------------------------------ [2002-02-21 04:01:05] ivo@ibuildings.nl The default (files). ------------------------------------------------------------------------ [2002-02-21 03:19:45] yohgaki@php.net What is your save handler? "files" or "user" or else? ------------------------------------------------------------------------ [2002-02-20 08:23:33] ivo@ibuildings.nl The value for gc_maxlifetime specifies after how long php sees stored session data as garbage. This is not correct behaviour. Example: Say, I have set gc_maxlifetime to 24 minutes. I start using an application that stores something in the session. I continue working for the next 24 minutes. Suddenly, the earliest session data (stored 24 minutes ago, but still used!) will be seen as garbage and disappears, rendering the application useless. It should only see the session data if the session is not used for gc_maxlifetime seconds. If I keep using the application, the session data should not be thrown away. (current workaround is to set gc_maxlifetime to something big, but that's not the correct solution in my opinion) ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=15644&edit=1