If I configure the SSLSessionCache directive to anything other than none or nonenotnull, I get a Seg fault reported in the error log when I try an HTTPS access, and my browser reports that the connection was interrupted while negotiating a connection. It works fine when I remove the directive, or set it to none or nonenotnull, and it works fine on unsecured http regardless of this directive. The directive is global, not in a vhost or any file/dir/location etc. Any thoughts on what's causing this or how to track down the cause of the segfault? Thanks -Brian -- Feel free to contact me using PGP Encryption: Key Id: 0x3AA70848 Available from: http://pgp.mit.edu/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx