You will need a second cert for the second domain.
If you have that much trouble configuring Apache, may I sugest seting
up a developement server to test and thrash around on. It is a
definate life saver, and low end a Linux box is cheap.
If a dev server is out of the question, you should try to keep the
old config around until the new config is working. That way you can
put the old config up while reading documentation, preparing another
attempt, sleep, eat etc.
As for virtual SSL hosts, just put all the SSL* directives (SSLEngin,
SSLCertificatFile, etc) into the appropriate <VirtualHost> section.
-Philip
On 31-Dec-98 John Baskind wrote:
> I currently run three domains as virtual hosts on a server which
> also runs
> three other virtual hosts which don't belong to me.
> (Apache_1.3.3/mod_ssl/mod_perl
>
> One of my domains runs a secure server on port 443 while allowing
> general
> access on port 80.
>
> Now I need to enable a second domain with a secure channel, with a
> cert in
> the name of the second domain.
> I am presuming that I will have to somehow make this happen in
> httpd.conf,
> but I can't think of a way round the basic problem. Unfortunately I
> can't
> take the server down for long periods of time, because of the three
> extraneous domains whose owners don't understand or enjoy my habit
> of
> server-upgrading.
>
> They all have bitter memories of my first install of mod_ssl, whose
> primary
> side-effect was 3 days of server downtime!
>
> Please can someone more knowledgeable point me in the right
> direction?
> ____________________________________________________________________
> __
> Apache Interface to SSLeay (mod_ssl)
> www.engelschall.com/sw/mod_ssl/
> Official Support Mailing List
> [EMAIL PROTECTED]
> Automated List Manager
> [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
