-
Notifications
You must be signed in to change notification settings - Fork 371
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
MaxAge checks against wrong value in Save func #96
Comments
You are probably right. I will working with session handling in the next couple of week and I will check it. |
As you could probably tell from my misplaced issue, I'm experiencing the same thing. I was using a MaxAge of 0 and after updating the package my application didn't work. I've made a temporary fix in my copy but this could easily trip up others as well. |
gorilla Session creation isn't handled correctly when MaxAge is unset. Work around upstream bug[1] by explicitly setting MaxAge. [1] gorilla/sessions#96
[Resolves gorilla#96]
I came across the same issue. So, if this hasn't yet been addressed in a subsequent release, how do I go about updating the code for my project? (new to GitHub) |
See #103 |
Closing; tracking in #103 |
@pappz @elithrar
in file store.go, line 216:
must be "session.Options.MaxAge < 0" because 0 value means browser expires cookie when you close the browser, but when it is "session.Options.MaxAge <= 0". it removes session file right away and when you want to "Save" session with MaxAge 0 for "until browser is open expiration time", Save function tries to delete file that not exists yet and os.Remove() in erase function returns "remove path\to\tempdir\session_: The system cannot find the file specified." PathError.
The text was updated successfully, but these errors were encountered: