Hi, i'm really exaggerated and I think I'll leave laravel. It's a good framework but It's not fu*king possible that there isn't a solution to a bug so bad. I'm working with laravel in a project and now Its almost one week that I search for a solution. My boss think I m proceding but so isn't. The bug is this: https://github.com/laravel/framework/issues/8172 . If anyone have a solution (any kind of solution) please tell me. Sorry for my english
What is your exact problem then? I see a lot of solutions in the thread and I also see a lot of issues, what is your exact issue? Did you try to update your local environment like everyone suggested?
For example when the application log in an user, there is a probability on which that user will be logged out. Also often the csrf token change and when I made a post call, laravel give me an error. However now I've disabled the csrf middleware and seems It's working fine. Now the user is no longer logged out
Well, there is a reason why CSRF is enabled by default! It makes your application saver.
I have build tons of Laravel applications and never had any issues with the CSRF stuff. I think we need to see parts of your code to see what's happening
There is no reason to see all the code because I've tried with a fresh installation of laravel and the issue was present. I know CSRF is for security but I've not alternatives.
We have recently got the same problem! We tried to use memcached for session handling but the sessions were constantly regenerating. Please check the config/session.php lifetime parameter. We made it more than 30 days long by mistake, so according to the documentation http://php.net/manual/en/memcached.expiration.php memcached considered the expiration time as a unixtime date to expire at. We were very surprised by the fact that laravel doesn't check this fact, but simply puts data to the memcached handler. So we have an interesting issue which is very difficult to detect, cause memchached returns success but the data transfered into the cache is already expired while we guess it is still fine.
Since 5.0, Laravel has REAL problems with session variables persisting. It's shades of CodeIgniter. Do a Google search for "Laravel sessions not persisting" and you'll see it's not isolated.