Hmm... one step further.
Google Chrome is filling in my username and password automatically, and somehow, when the App::before filter redirects the visitor back to the loginpage, the POST route that triggers the attempt login functionality is triggered. So the user is logged in again..
Okay, I fixed it by changing the POST route to a different URL.. Both my GET (show login view) and POST (attempt login) routes where using /login as the URI.
Apparently Chrome was automatically using the POST route when the username and password were set to be remembered by the browser.
Sign in to participate in this thread!
We'd like to thank these amazing companies for supporting us