Bug #49737
TYPO3.session.inactivityTimeout not working
| Status: | Closed | Start date: | 2013-07-06 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Session | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | Affected Flow version: | Git master |
Description
I'm logged in into the neos backend. After some idle time of doing nothing (don't know how much but like half an hour or so?), and realoading the page, i get redirected to the login page again.
I set the following in Configuration/Settings.yaml:
TYPO3:
session:
inactivityTimeout: 0
what i expect is that i can be logged in "forever". My session cookie has a lifetime of 1 year so that should not be the problem :D
History
#1 Updated by Robert Lemke about 2 years ago
- Status changed from New to Needs Feedback
Please post the corresponding message from your Flow System log, something like:
Session: Destroyed session with id OTNfzTHXILKkO05KIHYpvLRuPivlsOir: Session OTNfzTHXILKkO05KIHYpvLRuPivlsOir was inactive for 57149 seconds, more than the configured timeout of 3600 seconds.
#2 Updated by Simon Schaufelberger almost 2 years ago
here is my message:
Session: Destroyed session with id zog34Lk4Zr8UJiE19WAIlr0OqBphMioZ: Session zog34Lk4Zr8UJiE19WAIlr0OqBphMioZ was inactive for 22314 seconds, more than the configured timeout of 3600 seconds.
what a shame, i think it was my fault. The indention was not correct in my settings.yaml. i will test it again and let you know my result.
#3 Updated by Simon Schaufelberger almost 2 years ago
ok, it really works. you can close that issue.
#4 Updated by Bastian Waidelich over 1 year ago
- Status changed from Needs Feedback to Closed