On Fri, 18 Jan 2002, Owen Boyle wrote: > > My virtual hosts in httpd.conf are setup as following: > > > > <VirtualHost IP.114:443> > > Pathtocert1 > > Servername server.com > > </VirtualHost> > > > > <VirtualHost IP.115:443> > > Pathtocert2 > > Servername joe.server.com > > </VirtualHost> > > > > The results are, again, going to joe.server.com gives the same certificate > > as just going to server.com. Of course, I have two IP addresses designated > > to the same machine (.114 and .115). > > > > Am I on the right track? > > Kind of - you don't need to define SServerName since the IP address does > the defining. You get the selection in the browser - i.e. > https://ip.114/ and http://ip.115/ should go to the different hosts... >
You mean the browser takes the domain name from the browser, does a DNS lookup, and equates this to the IP, and because the IPs are differnet in my example, the Servername is not necessary? What if I wanted to setup something like the following: <VirtualHost IP.114:443> pathtocert1 Servername joe.com DocumentRoot /home/joe </VirtualHost> <VirtualHost IP.114:443> pathtocert1 Servername auty.com DocumentRoot /home/auty </VirtualHost> Because the IP is now ambigious, I'm assuming the Servername is required unless I used the NameVirtualHost * convention (which I haven't really gotten working with SSL in my brief attempts)? This (the above) seems to work as expected, although when I do a apachectl startssl I get an error message about the one taking precident over the other... the error message doesn't seem to affect any usage, it seems to work fine. Am I right? If not, is there a way to get around the error? -- Joe Auty [EMAIL PROTECTED] http://www.netmusician.org http://www.jeahost.com ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
