On Wed, 2003-03-19 at 01:47, Andre M. V. wrote: > Joon, > > if that's the case, then use ip based virtual > hosting with ssl rather than named based virtual > hosting. You can even mix named and ip virtual > hosting if you like. It's all in the apache docs. > > Again, additional external or public ip address > and configure the DNS and certs.
Yup, that's what I thought would be the only feasible solution. Good thing additional IP addresses aren't that costly. One more question: Should every additional external/public IP address map to different internal IPs, or could they all point to only one internal IP? The vhost directives in the httpd.conf file makes use of the internal IPs (eg <VirtualHost 192.168.0.1>), not external ones, so I guess it should be the former. And if I only have one ethernet interface, that means I should resort to using subinterfaces, right? Thanks Andre! And thanks to the others who replied to my query and provided suggestions. I probably would have some use for them at some point. :) -- Joon Guillen ================================ So computers are tools of the Devil? thought Newt. He had no problem believing it. Computers had to be the tools of _somebody_, and all he knew for certain is that it definitely wasn't him. from "Good Omens", Neil Gaiman & Terry Pratchett _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
