419 page expired

[blondie63]

Sometimes, when my session times out, I get this error on a dark gray screen:
419 | PAGE EXPIRED
Does anyone know how to fix it so that if the session expires it goes to login?

[jcastroa87]

Hello @blondie63 this happen mostly with the check of "CSRF token" so if there is a long wait time with no activity will expired and fail check.

Please let me know exactly where you receive this error message,

The reasons here could be:

• The page takes too long to send its request and, as such, the token expires (page expired).
• You probably did not add the @csrf blade code with your form, so the token expected from your form is not present.

Solutions:

• Solution for reason 1: Refresh the page.
• Solution for reason 2: Add @csrf just beneath the form.

Cheers.

[blondie63]

Hi @jorgetwgroup On my prj i'm only using BackPack Cruds, sometime, when i leave a List page open and minimize the browser, when i come back i see this:

[blondie63]

Hi @jorgetwgroup what you think about previous post?

[jcastroa87]

Hi @blondie63 maybe you can try this package: https://github.com/GeneaLabs/laravel-caffeine to not handle with session expired on your server.

Cheers.

[blondie63]

Thanks

[pxpm]

Hey guys. I am just going to tell from my experience here.
Please be aware that disabling the "expiration" with the caffeine package has the downside of adding a "pool" mechanism to every user visiting your website, and "idle/inactive users" would still consume resources to answer the pool request.

I think the best approach here would be to catch the TokenMismatchException in your App\Exceptions\Handler.php

public function register(): void
    {
        $this->reportable(function (Throwable $e) {
            if($e instanceof \Illuminate\Session\TokenMismatchException) {
                redirect('login');
            }
        });
    }

It should work fine for 95%+ of the use cases.

Cheers

[jcastroa87]

I'm closing this issue due to inactivity. If you need further assistance or have additional questions, feel free to reopen this issue or create a new one. We're here to help!