-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Session expires on logon form #8194
Comments
I'm not sure I understand the exact scenario. Session should not just expire. The logon form itself has it's own session, so if that expired then indeed you'll have to logon twice, but I'm not sure this is what you're talking about here. Are you talking about the case when session expires because user didn't have the internet connection for a while, or are you using some modifications that expire session depending on the session time? |
Yes, it is the case when user didn't have the internet connection for a while (operation system has been suspended) |
Then it might be two cases:
I guess it's the former, but confirm, please. |
I can't say exactly what happens. It could be the issue 1. |
As there's no other ticket for this issue, let's keep this open. No workarounds. |
We hit the same issue.
Meanwhile, session GC run and deletes the user session from database.
Maybe set longer |
You'll hit the timeout eventually no matter how big it is. The easiest workaround for me is to add reload script into the login page on browser tab activation:
It could be improved by delaying reload until session expired, but since it reloads almost instantly it is good enough for me. |
I'm getting rcmail::ERROR_INVALID_REQUEST (localized) message on the login screen after entering correct user name and password for the first time after session expiration. Second attempt is fine.
POST request returns 401:
Response Headers
Request Headers
Form Data
RoundCube Version: latest (but it is happening for at least a year on a different versions)
PHP: 7.4.19
Web Server: nginx + php-fpm
OS: linux
The text was updated successfully, but these errors were encountered: