I have just realised that the basic auth scaffolding that comes with laravel has logout as a GET request instead of a POST. From what I have read, logout requests should really be POST. I am just wondering if there is a particular reason it is GET instead?
Maybe that was a problem back in 2013 - I can't say if it was and if so how common it was - but I'm using Chrome with prediction enabled and I've never noticed being logged out of a website unwillingly
Also if that is such a big problem, there should be plenty of posts about it, try search the forum..
@SaeedPrez I know! That's why I created a post! I also don't see it as particularly big deal, I just understood it to be standard practice nowadays to make the logout a POST and wondered why it wasn't.
@_chris there are 9999999999 things to think/worry about when building a web application today, this is just one of them. We have to identify our needs and prioritize and not worry about every small detail. Especially when using such an awesome framework like Laravel which takes care of a lot of those worries out of the box.
If and when it ever becomes a problem that your visitors get logged out because of browser prediction, then you can worry about and spend time on refactoring your logout GET to POST.