Mark Weisman wrote: > > Working a little here with Apache couldn't you just make another VS > entry in Apache for the new port, all using a singular IP addr? > Example; > --<VirtualHost 120.120.120.120:80> > -- ServerAdmin [EMAIL PROTECTED] > -- DocumentRoot /www/domain1 > -- ServerName www.whatever.com > -- ErrorLog wherever > -- CustomLog wherever part two > --</VirtualHost> > --<VirtualHost 120.120.120.120:443> > -- ServerAdmin sameguy or gal > -- DocumentRoot /www/ssl > -- ServerName www.whatever.com > -- ErrorLog wherever > -- CustomLog wherever part two > --</VirtualHost> > > By allowing Apache to do the internal routing, wouldn't that re-direct > where he's talking about. I'm also doing a lot of virtual hosting, and > currently I use a singular domain name for all SSL requests I was > thinking about trying the above out and see if it worked? But since > we're on the topic.
What you have above is perfect. This is port-based virtula-hosting and there is no problem with it. The problem arises if you try name-based VHing with SSL - that won't work: http://www.modssl.org/docs/2.8/ssl_faq.html#ToC47 http://marc.theaimsgroup.com/?l=apache-modssl&m=98559369910170&w=2 Rgds, owen Boyle. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
