mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #35775
[Bug 1590293] A change has been merged
Reviewed: https://reviews.mahara.org/6582
Committed: https://git.mahara.org/mahara/mahara/commit/0913742c00380c77c79bf4b174684b9427e60a2b
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch: 16.04_STABLE
commit 0913742c00380c77c79bf4b174684b9427e60a2b
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date: Wed Jun 8 19:14:18 2016 +1200
Bug 1590293: Correcting inconsistencies in session expiration
1. Add some documentation to session.php explaining what
the session.gc_maxlifetime ini setting does.
2. If we can't access $CFG->session_timeout, use a timeout of
an hour instead of the PHP default of 24 minutes.
3. Limit $CFG->session_timeout to 30 days, because we're already
enforcing that limit in session.php
4. Add "usr_session.mtime" column so that we can delete old sessions
based on inactivity instead of creation date.
5. Make the cron delete old session files as soon as they've expired,
rather than padding that an additional two days.
Change-Id: I9da2b26217774566b1131e997724359715edb2fe
behatnotneeded: Covered by existing tests
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1590293
Title:
Inconsistencies in how we handle $CFG->session_timeout
Status in Mahara:
Fix Committed
Status in Mahara 16.04 series:
Fix Committed
Status in Mahara 16.10 series:
Fix Committed
Bug description:
While researching bug 1588613 I noticed several inconsistencies in how
we handle the $CFG->session_timeout setting. This patch will clean
those up and make things more consistent across the board.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1590293/+subscriptions
References