I have read many posts about the inability to use virtual host names with ssl. My
firewall uses NAT, and only allows one LAN IP to receive requests for httpd on ports
80 and 443. Given that I can have multiple IP's on one NIC (i'm running Redhat Linux
7.2) and that I can setup my internal DNS (which the firewall uses) such that:
SITE IP
-----------------------
www.site1.org 192.168.0.1
www.site2.com 192.168.0.2
www.site3.net 192.168.0.3
...
And putting the following in my httpd.conf:
NameVirtualHost 192.168.0.1:80
NameVirtualHost 192.168.0.1:443
NameVirtualHost 192.168.0.2:80
NameVirtualHost 192.168.0.2:443
<VirtualHost 192.168.0.1:80>
ServerName www.site1.org
...
</VirtualHost>
<VirtualHost 192.168.0.1:443>
ServerName www.site1.org
...
SSLCertificateFile ...
SSLCertificateKeyFile ...
</VirtualHost>
<VirtualHost 192.168.0.2:80>
ServerName www.site2.com
...
</VirtualHost>
<VirtualHost 192.168.0.2:443>
ServerName www.site2.com
...
SSLCertificateFile ...
SSLCertificateKeyFile ...
</VirtualHost>
Assuming that the firewall sends httpd requests to 192.168.0.1, is it possible for
apache to be configured to handle requests made to www.site2.com/192.168.0.2? Or can I
accomplish what I desire by using some sort of proxy that receives all httpd requests
from the firewall and then connects to my apache server.
I guess my bottom line question is - can I use internal IP addresses to use multiple
ssl-enabled virtual hosts, and if so, how?
Regards,
Michael
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
