Hi, What about if one is using certificate like *.my.site? I expect then it will be possible to host all virtual host on the same IP address even in HTTPS mode... Rossen ----- Original Message ----- From: "Owen Boyle" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 09, 2001 7:14 AM Subject: Re: confusing phenomenon with mod_ssl in apache chroot > hendy wrote: > > > you are attempting NBVH with SSL (which is not possible). > > > it is possible - the mod_ssl error is not fatal - it just uses the same > > certificate (which in cases of *.foobar.com is an acceptable solution - at > > least for me). > > Just for the record, proper NBVH cannot work with SSL for reasons which > are fundamental to the HTTP protocol. In a nutshell, SSL negotiation > (needing the certificate) is done *before* the ServerName (defining the > certificate) is transmitted. It is true that if you don't care what > certificate gets used it will *seem* to work but what really happens is > that apache takes the certificate from the first VH in httpd.conf which > is assigned to port 443. > > Proper NBVH requires that distinct sites can share the same IP address > and port number. This cannot be supported using SSL. > > However, since you have several IP addresses you *can* have many SSL VHs > on the same machine - just assign them all different IPs. > > Anyway, glad you got it working eventually. You've got me worried about > this IPv6 patch though... > > Rgds, > Owen Boyle. > ______________________________________________________________________ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
