[Tickets #1658] NEW: setting session timeout to non-zero expires sessions immediately

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1658
-----------------------------------------------------------------------
 Ticket             | 1658
 Created By         | amy.rich at tufts.edu
 Summary            | setting session timeout to non-zero expires sessions immediately
 Queue              | Horde Base
 Version            | 3.0.2
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


amy.rich at tufts.edu (2005-03-31 17:55) wrote:

There seems to be an issue with the session timeout defined in
horde/config/conf.php.  We wanted the horde session to time out before our
load balancer so the user would get any meaningful messages before the load
balancer cut the connection.  In order to make this
happen, we set the following timeout:

$conf['session']['timeout'] = 3300;

This resulted in sessions expiring immediately, so there was a looping
problem when we tried to use hordeauth for imp since the credentials were
always different.

Setting the timout back to the default of 0 fixed the problem.  Setting it
to time() + 3300 also appeared to work, but is very inellegant.