Hot to forget user session when browser is closed? Laravel 5.6.

https://laracasts.com/discuss/channels/laravel/session-expire-on-close

Check @Snapey reply, and maybe @jlrdw solution

i'll check it dude @vilfago Thanks... but looking for more idea in Laravel new version.

but looking for more idea in Laravel new version

Session and cookies have not changed over the versions. If you did not setup remember me then user should be logged out if they close the browser.

Also, remind users to log out, hat doesn't hurt.

Many Banks even post a notice advising users to close the browser even if they did logout, just for added security.

@jIrdw Where should i setup this "remember me "?

No you don't want"remember me " if you want user logged out.

@jlrdw ahh okay man, so you have idea how to destroy the session?

@jlrdw remember me doesn't work to me.

Look at the /config/session.php file. It has this as default

/*
    |--------------------------------------------------------------------------
    | Session Lifetime
    |--------------------------------------------------------------------------
    |
    | Here you may specify the number of minutes that you wish the session
    | to be allowed to remain idle before it expires. If you want them
    | to immediately expire on the browser closing, set that option.
    |
    */

    'lifetime' => env('SESSION_LIFETIME', 120),

    'expire_on_close' => false,

change expire_on_close to true

@Cronix Thanks sir, already done that implementation...

Upon checking in my table in database sir why user_id is not null? When you used Auth::logout() the user_id is null... Is this not an issue? I've been curios on this observation.

I'm not sure if that matters. Once you close the browser and reopen it and navigate to your site, are you still logged in?

sir @Cronix Can we add some code on the expire_on_close (original file)?

You can override anything in laravel. But, can you answer the question I asked? Are you still logged in if you close the browser or tab, reopen it and navigate to the site? The entries in the sessions table will get deleted naturally so you don't need to worry about that if that's what you're thinking. It just doesn't happen immediately (either do regular php sessions without laravel)

Sorry I didn't notice your question sir @Cronix... Nope the User was logged out.. but when you login that user back new session id will be occurred for that but the old session id of that user is still active(I don't if it's the right term)... As what i tested:

1. I logout specific user using Auth::logout(); and check database (session table) the user_id is returned to null.

2. I closed the browser and re-open the browser again (with the link) the user was logged out. But when I checked the database (session table) the user_id was not return to null, instead a new session id was added to that user.

As I mentioned, don't worry about the data in the sessions db table. The stale sessions will be automatically deleted eventually. It uses a lottery system, so it's not immediate. They don't do anything though, as you can see because the user is still logged out when you revisit the site and they have to login again, which is what you were wanting.

Edit: If you want to increase the chances of the session being removed from the sessions table, the setting is again in /config/session.php

/*
    |--------------------------------------------------------------------------
    | Session Sweeping Lottery
    |--------------------------------------------------------------------------
    |
    | Some session drivers must manually sweep their storage location to get
    | rid of old sessions from storage. Here are the chances that it will
    | happen on a given request. By default, the odds are 2 out of 100.
    |
    */

    'lottery' => [2, 100],

However, I'd leave it. It can be an intensive process, and it's unnecessary to change unless you have millions of users and need the db space for performance reasons.

Okay sir Thank you for the additional info.. you answered my curiosity..

  $users = Session::whereNotNull('user_id')->get();

This was i used to list all active user that's why I curios because in my view there's a lot of list when only 3 users are logged in.

Ah, yeah I wouldn't do that. It's not accurate. If you really need to, I'd add an additional constraint to your query.

$users = Session::whereNotNull('user_id')
    ->where('last_activity', '>=', now()->subMinutes(10)) // active in last 10 minutes
    ->get();

Yeah sir that's now what I implemented.. but I missed subMinutes(10)

   $users = Session::where('last_active_at', '>=', now()->subMinute())->whereNotNull('user_id')->get();

Thanks again sir.. I need now to make a cron job to refresh my connection monitoring view every 5 mins.

sir @Cronix is this right? I need to refresh the table in a div (#monitoring)

   (function () {
    setInterval(function () {
        axios.get('pages.admin.system.connection-monitoring.index',)
            .then(function(response){
                    document.querySelector('#monitoring')
                            .innerHtml(response.data);
            }); // do nothing for error - leaving old content.
        }); 
    }, 300 000); // mi