Apache 2, SSL and Virtual Hosts

[xlargebear at bellsouth.net]

Hi Randy
Thanks for your reply.
I have set up VirtualHosts using the different ports method (443,  
444, and 445). However, I'd like to use the standard port 443 for all  
of them. Therefore, I think that creating aliases on my network  
interface would be the way to go for me. I have one question though.  
Let's say the IP of the webserver is 10.0.0.10 and I make two  
aliases: 10.0.0.11 and 10.0.0.12. On my router I'd forward port 443  
to IP 10.0.0.10. How will the other two aliases get the traffic  
directed to its virtualhosts if port 443 only points to the first  
virtualhost?
EJ

On Jun 13, 2005, at 1:11 PM, frenzy at frenzy.org wrote:

> This is a function of the way SSL certs work. If you want separate  
> certs
> on each virtualhost, they each need a separate IP. This is because  
> of the
> SSL key exchange process.
>
> ie, change
> <VirtualHost www.domain1.com:443>
> to
> NameVirtualHost x.x.x.x
> <VirtualHost x.x.x.x:443>
>
> Alternatively, you could do a different port for each HTTPS  
> virtualhost.
> ie, 443,444,445, etc. I've heard this works but never attempted  
> myself.
>
> IP aliases on a network interface work great if you don't
> want to put in extra network cards.
>
> You could also just have one domain host all the secure webpages for
> the other two domains.
>
> Cheers,
>
> Randy
>
> http://www.frenzy.org
> "Sed Quis Custodiet Ipsos Custodes?" -Juvenal
>
>
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords>  
> site:terrasoftsolutions.com'
>