Justin Pasher wrote:
So are you suggesting that I need multiple public IPs to implement this, or just multiple private IPs? Private IPs is not a problem, however, due to the fact that we have limited public IPS in our range, it could be a problem when if and when we add new SSL certs. We would need to re-evaluate our ISP contract before it expires.Serge Fonville wrote:Hi,My company is wanting to keep this configuration for port 80 and add an SSL certificate for just the www.example.com and example.com hostnames. Isit possible to have Virtualhosts for just the 443 port and still allow *.example.com to react the same way it does now?Yes, it is. However, you'll generally need separate IP addresses for www.example.com and example.com. Then just define the virtual hosts <VirtualHost 12.34.56.78:443> </VirtualHost> <VirtualHost 12.34.56.79:443> </VirtualHost>Not neccesarily, You can use virtualdocumentroot instead of virtualhosts. Almost all config in virtualhosts directives can also be done in htaccess, which you can even put one level higher.I believe he recommended multiple VirtualHost containers because the OP was asking about essentially two SSL sites (www.example.com and example.com), which requires individual IP address to get universal browser support (i.e. without SNI). Even with a wildcard cert for *.example.com, I don't believe that will work to example.com.
Dan Schaefer Web Developer/Systems Analyst Performance Administration Corp. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|