U++ forum: Welcome to the forum

Re: sessions in Skylark [message #38381 is a reply to message #38375]

Thu, 13 December 2012 08:07

dolik.rce
Messages: 1792
Registered: August 2008
Location: Czech Republic

Ultimate Contributor

Hi Peter,

I'm not exactly sure what is the problem, but there is a couple things you might or might not now:

The session storage is cleaned only once every 10 minutes. So setting session_expire in config file or SkylarkSessionConfig::expire to anything less then 600 doesn't make much sense.

The session variables are stored in cookies. The fact that Firefox behaves differently is probably caused by different cookie cleaning settings.

The expiration time for session is counted since last write (any call to SetSession(), NewSessionId(), NewIdentity() or SetLanguage()).

Http::ClearSession() seems to currently only delete the session variables "temporarily" - if you don't write anything new into the session, it will not be reset. I'm not sure if it is a bug or intended behavior. I think that if you want to get rid of the current session variables it is safer to call NewSessionId().

If none of the hints above helps you, let me know. I'll try to make an example application demonstrating how to use the session functionality for user logins.

Best regards,
Honza

Report message to a moderator