-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Make sessions never expire with $config['sess_expiration'] = -1 #3677
Comments
The answer is simple - no. This is a really bad idea and we won't be encouraging this type of thing. Although you're free to increase the |
Why is it a bad idea? Frameworks shouldn't constraint design choices. |
But at the same time, the framework shouldn't encourage using bad/insecure design choices. That's why it won't be implemented into the core. You can read more about session management recommendations here. Nothing stops you from setting |
You have no idea about the system we are creating, requirements, audience, etc. You are encouraging silly workarounds based on unfounded mind-reading skills which you do not have. |
A never expiring session is a really bad idea, in terms of security. You are practically inviting hackers to exploit your web app by using session-based attacks. This is not a silly design choice. What you are proposing into the core is rather insecure. Users would not want to use a framework that is promoting vulnerabilities within itself. |
I agree with you that I have no idea about the system you're creating, its requirements, etc. but even if the idea of the never expiring session may fit your project's needs it certainly doesn't fit the framework's core. Sorry. |
According to the documentation:
sess_expiration > 0 => "The number of SECONDS you want the session to last."
sess_expiration = 0 => "Setting to 0 (zero) means expire when the browser is closed."
Can we please have a -1 configuration, for sessions that never expire?
Thank you.
The text was updated successfully, but these errors were encountered: