Login, Session or Cache problem?

[eluser]tonanbarbarian[/eluser]
I was talking about the Cookie expiry time.
If the cookie is set to expire as well as the session and the server time is incorrect the cookie will expire and not be sent back to the server, even if the server session time is still valid
If the session code being used also sets expiry time on the cookie the issue could appear

[eluser]mixmike[/eluser]
Yes, you are correct.

I think one way of getting around this would be to store the session id in the cookie and store the time on the server. Everytime you get a request, the browser would send the session id in the cookie. The server would check for the expiration time for that session id and process the request as required.

I'm pretty sure some of the session libraries are already doing this so you should be able to get around the problem without having to write your own session implementation (unless you want to).

[eluser]tonanbarbarian[/eluser]
yes but you have to make sure that you set the expiry time of the cookie far enough into the future that it does not expire, taking the server time out of the equation

[eluser]codelearn[/eluser]
[quote author="mixmike" date="1196818795"]Codelearn, it could be an issue specific to IE. You could spend a lot of time trying to figure it out... or simply use the session that works with any browser. I don't know enough to help you futher with this. To me, it wasn't worth it to debug the problem in ci_session. I just switched to the native library.
[/quote]

Mike,

I believe that Site Sentry is created with the requirement that you use ci_sessions table. I don't think the native library uses a db...