The way I get around that is to "make" my certificate for just domain.com .. then have all my virtual hosts like mail.domain.com and admin.domain.com or whatever else... all ofcourse only use the domain.com cert file, however, with a cert for domain.com and a hostname of mail.domain.com, the web browser doesnt complain TOO much... :)
--On Friday, January 17, 2003 02:52:44 PM -0700 Dax Kelson <dax@gurulabs.com> wrote:
On 17 Jan 2003, Mr. Adam ALLEN wrote:I'm experiencing problems with Apache, doing name based virtual hosting for SSL sites.This is not possible....In fact, I just wrote about it. "The HTTPS protocol requires that an SSL handshake occur as the very first step. During the SSL handshake the web server sends the client it's certificate. The certificate contains the FQDN of the web server. For named-based virtual HTTPS hosting to work, the web server would have to know which certificate to send to the client during the SSL handshake. The server doesn't know this until the client sends the Host header -- transmitted after a successful SSL handshake. Therefore, virtual hosting SSL sites requires the use of unique IP addresses for each site." Dax Kelson Guru Labs -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
-- Tommy McNeely -- Tommy.McNeely@Sun.COM Sun Microsystems - IT Ops - Broomfield Campus Support Phone: x50888 / 303-464-4888 -- Fax: 720-566-3168 -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
