-
Notifications
You must be signed in to change notification settings - Fork 56
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
Unexpected session expiry #2690
Comments
Hey @xaur the login is required in order to renew your CSRF token, hence the modal is displayed for every action that requires a valid CSRF. See #2541. On the other tab, the login is still active because you were never logged out, but it will also display the error message for expired sessions. Thanks. |
Sorry I don't quite follow, but let me reword what I observed:
It is confusing to see the modal it if my session is not really expiring. |
hmm can you give us a concrete example or some links of this happening? How long did your "slowly reading" take? Was it like more than one day? Was it displayed during your session (while you navigate without taking more than 24h)? Do you have your localStorage enabled on your env? |
The proposal link was this. I don't remember how long I had the browser tab open at this point, it could have been less or more than 24h, or both. I'm pretty sure I had instances when the popup appeared after like an hour or less of the tab being open. I just "got rid" of it with page refresh and continued comment voting, because I knew the session must be longer. localStorage is enabled and without it Politeia won't load. Firefox reports Politeia consumes 44 KiB of data as of writing. Let me know if I can provide anything else to hunt it down. |
I'm reading through a long tree of comments and periodically a "Session expired" modal pops up in response to my actions (comment upvotes) and asks me to log in. I must add that it eats a lot of CPU to do so.
I cancel the modal and refresh the page or open the same link in another tab, and remain logged in, so I guess it's a false error. There appears to be "page session" and "login session" with different timeouts.
The text was updated successfully, but these errors were encountered: