"Ralf S. Engelschall" <[EMAIL PROTECTED]> writes:
> On Thu, Dec 30, 1999, Tom Vaughan wrote:
>
> > A long while back, ssl sessions were expired every 100 server restarts. For
> > a busy server that stayed up a long while, this was less than
> > optimal. Currently ssl sessions are expired on each server start and
> > restart, session cache store and retrieve. Doing this on a server start or
> > restart is not necessary since the session cache is truncated. And doing
> > this on each store and retrieve seems a bit excessive to me. How about
> > expiring ssl sessions when a connection is closed?
>
> Hmmm... for SHM based session caches it should not make much difference,
> of course. But for DBM based session caches you're right, there it can
> be more reasonable to run the expire job on connection close. Hmmm....
> but I've to admit that currently I have no real opinion on this. I'm
> very unsure what the best/most reasonable approach is. What is the
> opinion of others on this topic?
Ideally it would be nice if Apache had an "every so often do this" module
hook. And by "do this" I mean "call an appropriate module callback", not
"invoke this script". And it would be doubly nice if the module could
specify how often "this" is done. Like every 100 requests, or every hour.
Just some thoughts...
-Tom
--
Tom Vaughan <tvaughan at aventail dot com>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
