Dave et al, You are thinking about TLS/SNI (Server Name Indication). It is offered by mod_gnutls and is to be supported in future releases of apache. Warning, it is not supported by all browsers (for example not in any XP IE).
If you want to see it in action, visit this url (use both firefox and XP IE to see the difference) https://sni.velox.ch/ sue fritz From: Vermont Area Group of Unix Enthusiasts [mailto:[email protected]] On Behalf Of Dave Tisdell Sent: Wednesday, March 18, 2009 11:22 AM To: [email protected] Subject: Re: apache ssl configuration question Hi Mike, Multiple SSL sites on name based virtual hosts are unsupported although I read about a hack to accomplish it (completely unsupported by Apache and I don't remember where I saw it). You must use IP based virtual hosts. Dave David Tisdell. Music Teacher Browns River Middle School [email protected] (e-mail) >>> Mike Raley <[email protected]> 3/18/2009 8:40 AM >>> Greeting Vagueites I have a question related to apache using ssl. So, I have two virtual hosts defined, and working, no problem. Let's call them subdomain1.domain.com and subdomain2.domain.com. The first virtual host uses ssl for login and another section of the site forced to https through the use of an htaccess file. All works wonderfully. Now, The second virtual host is the new version/release of the first subdomain. So, same domain name, but wildly different code and directory structure. http works fine, https on the other hand... not so much. Now the ssl cert I have is signed by a trusted signer and is a wildcard cert. eg *.domain.com. I've been trying to figure out how to get the ssl.conf virtualhost settings correct for both of these virtual hosts. Admittedly I'm sick as dog, and hopped up on medication, but for th life of me I can't figure out how to get it configured. I'm starting to worry that even tho what I want to do is reasonable, it my not be possible, eg: http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts Tho, it is the same cert, and it is a wildcard, and even tho they are both on the same ip address... is it because using name based virtual hosts, the non default ssl virtual host entry in ssl.conf will never be hit? Any advice/ input would be most welcome. I apologize now if my addled brain has forgotten something. thanks! Mike This e-mail may contain information protected under the Family Educational Rights and Privacy Act (FERPA). If this e-mail contains student information and you are not entitled to access such information under FERPA, please notify the sender. Federal regulations require that you destroy this e-mail without reviewing it and you may not forward it to anyone.
