You might consider updating the versions of Apache and mod-ssl to something
more current (i.e. Apache 1.3.20).
Are there any 'external' issues that may be causing problems ? Do you have
2 or more DNS servers being used to look up the system name that the SSL
site is being hosted on (and the 1st
That's odd that you didn't have it in your httpd.conf file... Here's
what's in mine, which is the default file that comes with the 'source'
distribution...
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First either `none'
# or `dbm:/path/to/file' for the mechanism to
As long as the 'name' that the client (browser) used to access the website,
matches the 'name' on the certificate AND the servername for that
'virtual' (or 'real') host, it will work
If the certificate has the name store.domain.com embedded in it, then the
Apache 'server' will have to have
The Common Name that you use to 'build' the certificate must match the
ServerName that the webserver is 'projecting'.
You can have many ServerName entries in an Apache configuration if you're
running 'virtual hosts'... (but you'd need a different set of certs for each
name).
SO, if you built
: Kory Hamzeh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 22, 2001 3:55 PM
Subject: RE: newbie question about SSL certificates and hostname
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Steve Brazill
As long as the 'name
Yes, usually you'd use a different 'domain' name for the SSL content (i.e.
http://www.teletubbies.com and wwws.teletubbies.com or
secure.teletubbies.com) which helps keep things 'clear' when you're
switching back and forth between 'secure' and 'unsecure' modes. You'll
have to specify the
OK... I have successfully built a Solaris-8
x86 system (on a Compaq 1850R) which includes installations of MySQL/Apache/PHP
and "mod_ssl"...
I also had many trials and tribulations during the
process, but here's what I found that will help you (and future Sun x86
installers) complete the
