Link to home
Start Free TrialLog in
Avatar of Web_Sight
Web_Sight

asked on

How To Make The Session Expire After A Browser Close

Hi All,

I have a cakephp application with login facilty, after close the browser without logging out when you go back into project before the session has timed out you go straight to the User Manager screen. How we prevent it.

Thanks in advance.
Avatar of Rok-Kralj
Rok-Kralj
Flag of Slovenia image

http://php.net/manual/en/function.setcookie.php

If you specify 0 for $time parameter, the session cookie will last only until browser window (or tab) is closed.
Avatar of Web_Sight
Web_Sight

ASKER

Hi, i am using cakephp project and in core file i set Configure::write('Session.timeout', '18');
Then this should work.
Configure::write('Session.timeout', '0');

Open in new window

hi, normally we need 30mins session , thats why we put Configure::write('Session.timeout', '18');, the problem is that when we close the browser it still working.
Avatar of p_nuts
change the php session max time and leave cake to 0
ASKER CERTIFIED SOLUTION
Avatar of NeoAshura
NeoAshura
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
"the problem is that when we close the browser it still working."

The problem may be that you have more than on instance of the browser running.  Either a window or a tab will cause the symptom.

All instances of the same browsers all share the same cookie jar.  If you close one instance of the browser, but not all instances of the browser, the cookies will still be there, and they will persist until the last instance of the browser is closed.  So to get the session to expire, you must close ALL instances of the browser.  Then start a new browser window, go back to the site and see if you're OK.

Sorry, but it just works that way.  There is no workaround that I know of.
the only way i can think of is not use session cookies and build the session in every link / post ...
@Ray: One workaround is that a website "pings" server every minute or so... When you don't receive the ping for 2 minutes, you destroy the session.

This is a solution, but not the one I'd recommend.
@Rok-Kralj: Interesting.  Can you show us a code sample to illustrate how that would be done?
As I said, I'd not recommend it, because it can be heavy with server resources, and not so trivial to implement securely.

The simplest way it would be:

<iframe src="i_am_active.php"></iframe>

And then javascript that would refresh this page every 10 seconds, and every time it does, a php script would update user's database LASTPING (time()).

Then you would check lastping data on next ping/page load, and if they are more than 10 seconds in the past, then you know the page was closed.
And it is not 100% sure way, because if user closes browser and opens it again within this 10 second treshold, this wouldn't count as "browser closed". There is no 100% accurate soulition, because there is no reliable js API to detect such data.

There is also a solution relyiong on onclose javascript event, but is easily bypassed.