From:             [EMAIL PROTECTED]
Operating system: Redhat Linux
PHP version:      4.1.1
PHP Bug Type:     Session related
Bug description:  Wrong behaviour session.gc_maxlifetime

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 bug report at http://bugs.php.net/?id=15644&edit=1
-- 
Fixed in CVS:        http://bugs.php.net/fix.php?id=15644&r=fixedcvs
Fixed in release:    http://bugs.php.net/fix.php?id=15644&r=alreadyfixed
Need backtrace:      http://bugs.php.net/fix.php?id=15644&r=needtrace
Try newer version:   http://bugs.php.net/fix.php?id=15644&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=15644&r=support
Expected behavior:   http://bugs.php.net/fix.php?id=15644&r=notwrong
Not enough info:     http://bugs.php.net/fix.php?id=15644&r=notenoughinfo
Submitted twice:     http://bugs.php.net/fix.php?id=15644&r=submittedtwice

Reply via email to