On Thu, Aug 12, 1999, [EMAIL PROTECTED] wrote:
> [...]
> > What about applying the allowed cipher mask to sessions grabbed from the cache?
> > Or something like storing the cipher mask in the database and clearing the
> > cache only when it changes.
>
> Err... but if preserving the cache means that the server *will* behave
> differently then from how it is configured, then the cache *should* be
> cleared. This is sort of like not having your .c's dependent on your
> Makefile IMHO.
>
> I suppose you could run through all the cache entries and make sure they
> jive with the server's configuration, and then remove the ones that
> don't.
I've still not checked the technical possibilities, but I guess
this isn't easy to accomplish.
> Or you could just add an option to mod_ssl to unlink, or not, the
> cache files on starts and re-starts. With the default set to the current
> behavior.
This would be a reasonable approach, yes. We can use something like
`SSLOptions +PurgeCacheOnStartup' in httpd.conf, how about this?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
