|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #15644 Wrong behaviour session.gc_maxlifetime
Submitted: 2002-02-20 08:23 UTC Modified: 2002-05-02 00:00 UTC
From: ivo at ibuildings dot nl Assigned:
Status: No Feedback Package: Session related
PHP Version: 4.1.1 OS: Redhat Linux
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2002-02-20 08:23 UTC] ivo at ibuildings dot 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)


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-02-21 03:19 UTC]
What is your save handler? "files" or "user" or else?
 [2002-02-21 04:01 UTC] ivo at ibuildings dot nl
The default (files).
 [2002-02-21 05:32 UTC]
I need to take a look at code...
But before I do that, could you verify if this problem exists in CVS version?
 [2002-05-02 00:00 UTC] php-bugs at lists dot php dot net
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".
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Jul 16 15:01:28 2024 UTC