I've noticed this as well with the things I've been doing for sessions.
They way I understand it is that the server side session storing values is
supposed to expire after a certain lenght of time. I currently have this
at default so I think it should expire after 24 mins. The cleanup is done
within php itself so nothing is cleaned up until php is called again. Is
this correct? If so, I have sessions located within my /tmp directory that
are over 3 weeks old and have been there ever since they were first
On Wed, 4 Dec 2002, Tom Rogers wrote:
> Wednesday, December 4, 2002, 4:01:07 AM, you wrote:
> >> Ive just been getting myself deep into using sessions.
> >> Sessions are working as it should except for one condition.
> >> Say I log into the site, and the session is started, and I don't do
> >> anything for the next 30 mins, then go back to the site.
> >> Im temporarily logged out, but because the session cookie is still
> JWH> good,
> >> the next page load logs me back in.
> >> How do the people who use sessions handle this type of scenario??
> JWH> Whether your logged back in or not is dependant on your program. Once
> JWH> you are gone for over X minutes, your session file is deleted. So, even
> JWH> though the cookie is still good, the session will not have any data.
> JWH> What's usually done is to check for a certain session value, like
> JWH> $_SESSION['logged_in'] and if it's present, then continue, otherwise
> JWH> force the user to log back in again.
> JWH> ---John Holmes...
> Not quite that simple as the cleanup proccess may not have run and the data is
> still sitting there, I use msession so I am not sure if the normal session stuff
> will return expired data after it expires and before it is deleted....msession
> does so I hacked it to cleanup if expired data is requested.
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php