At 10:23 PM 2/12/00 -0500, you wrote:
I have heard you can host another cert by just creating another <Virtual Host>directive in your httpsd.conf file, but I have not tried it nor verified it so Ido not know if it works. It should if you use another IP.
Dennis, you definitely need an IP# per certificate. The reason is simple. Name-based hosting is done by examining the header that shows which URL you're calling. Apache can't see the headers on a secure transaction until after the secure server decrypts the incoming data, using the certificate, so it wouldn't know how to assign a certificate to incoming data until after it was decrypted, a catch 22 if I ever saw one <smile>.
The only way around it is to assign certificates by IP#; the target IP# is available before the header is decrypted.
Jeff -- Jeff Lasman <jblists@xxxxxxxxxxxxx>