#69763Re-login after expired backend session throws exception
Description
After BE session expires you get a lightbox popup (‘Refresh Login to TYPO3’) which allows you to enter your password and login again.
When doing this, the backend sometimes throws an exception: #1425389455: Invalid request for route "/main"
This appears to happen when you had an editing form open when the session expired. As a workaround you can remove the token from the url and login again with the normal login box.
Strangely, testing this with a really low value for [BE][sessionTimeout] did not reproduce this error. Could it be that the token has its own time-out value?
You can reproduce the exception by manually modifying the token in the url (but that is correct of course).
Reviews 7
- TYPO3_6-2 50703[BUGFIX] Update session id in user property
- TYPO3_7-6 50702[BUGFIX] Update session id in user property
- main 50701[BUGFIX] Update session id in user property
- TYPO3_7-6 50689[FOLLOWUP][BUGFIX] Redirect BE user to login on invalid module/route token
- main 50688[FOLLOWUP][BUGFIX] Redirect BE user to login on invalid module/route token
- main 50660[BUGFIX] Redirect BE user to login on invalid module/route token
- TYPO3_7-6 50687[BUGFIX] Redirect BE user to login on invalid module/route token
Related issues 5
- Bug #66242CSRF problem after relogin
- Bug #69277Invalid request for route "/logout"
- Bug #78739Internal user data is not updated when session id is regenerated
- Bug #82118User interface does not react / 500 internal server error dummyToken
- Bug #85844Invalid request for route "/ajax/system-information/render" after session timed out