-
Notifications
You must be signed in to change notification settings - Fork 70
Cookie expire time incorrect (Laravel 5.2) #42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Does the same setup work when you're serving via apache/nginx instead of php-pm? |
looks like your timesettings are wrong. php-pm doesnt do anything special with cookies lifetime. |
With nginx+php-fpm all works properly. Time settings also correct. |
httpkernel-adapter modifying cookie lifetime. |
According to http://stackoverflow.com/questions/21120882/the-date-time-format-used-in-http-headers it needs be GMT. So- where do we go wrong here? I also don't see why- if its wrong- this would differ from nginx and apache? |
This describes only date format. But gmdate() returns a Greenwich time (time from "0" timezone). |
Could you push a small PR?
|
So, seems to me, we're doing right. Is your timezone correctly set in php.ini (not of fpm/,cli/, but from cgi/ folder)? gmdate doesn't return from 0 timezone, but from your set timezone. If this is wrong, gmdate will return wrong results. Since on ubuntu fpm/cgi/cli have different php.ini files chances are high you have just put your server-timezone into the wrong php.ini. |
To make it more clear: on my ubuntu for example |
ping @isopropil is this still an issue? |
Closing due to missing feedback |
Trying to use with Laravel 5.2.
When Laravel set a cookie (session and csrf token), the expiration time of this cookies is in past.
Standart Laravel cookie lifetime - 2 hours, but I receive a cookie, that expired a hour ago. My current timezone - +0300. What happens?
Thank you.
The text was updated successfully, but these errors were encountered: