If you do not log in for a long time on the login interface, "Page Expire" will appear when you log in again. #4415

Closed
opened 2026-02-05 08:50:34 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @VincentZhang777 on GitHub (Jan 19, 2024).

Describe the Bug

If you do not log in for a long time on the login interface, "Page Expire" will appear when you log in again.
image

Steps to Reproduce

1.Open the Login Page
2.Idle Time
3.Attempt to Log In
4.Observe the Behavior

Expected Behaviour

Upon attempting to log in after inactivity, a "Page Expire" message is displayed, preventing login.

Screenshots or Additional Context

No response

Browser Details

No response

Exact BookStack Version

v24.1.19

Originally created by @VincentZhang777 on GitHub (Jan 19, 2024). ### Describe the Bug If you do not log in for a long time on the login interface, "Page Expire" will appear when you log in again. ![image](https://github.com/BookStackApp/BookStack/assets/153426621/9b805885-5e50-4eb1-9c17-bb0dacb5e8f9) ### Steps to Reproduce 1.Open the Login Page 2.Idle Time 3.Attempt to Log In 4.Observe the Behavior ### Expected Behaviour Upon attempting to log in after inactivity, a "Page Expire" message is displayed, preventing login. ### Screenshots or Additional Context _No response_ ### Browser Details _No response_ ### Exact BookStack Version v24.1.19
OVERLORD added the 🐛 Bug label 2026-02-05 08:50:34 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Jan 19, 2024):

Hi @VincentZhang777,
Thanks for raising, but this is expected since your session would have invalidated so the form submission couldn't pass CSRF checks.

While this could be an annoyance, I don't think it's a large enough one to work around with extra complexity since this specific case (of waiting on a page before performing an action) has rarely been raised, if at all in the past.

@ssddanbrown commented on GitHub (Jan 19, 2024): Hi @VincentZhang777, Thanks for raising, but this is expected since your session would have invalidated so the form submission couldn't pass CSRF checks. While this could be an annoyance, I don't think it's a large enough one to work around with extra complexity since this specific case (of waiting on a page before performing an action) has rarely been raised, if at all in the past.
Author
Owner

@szabeszg commented on GitHub (Jan 20, 2024):

Perhaps JavaScript could be used to monitor the length of idle time and respond accordingly, such as reloading the page. Would implementing something like that introduce additional complexity?

@szabeszg commented on GitHub (Jan 20, 2024): Perhaps JavaScript could be used to monitor the length of idle time and respond accordingly, such as reloading the page. Would implementing something like that introduce additional complexity?
Author
Owner

@ssddanbrown commented on GitHub (Feb 25, 2025):

@szabeszg yes.

Since there's been little further reported annoyance with this, and for the responses provided in my prior comment, I'm going to go ahead and close this off.

@ssddanbrown commented on GitHub (Feb 25, 2025): @szabeszg yes. Since there's been little further reported annoyance with this, and for the responses provided in my prior comment, I'm going to go ahead and close this off.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#4415