Thanks for all the replies! I figured out a way I could test the servers while I'm waiting for DNS changes to propagate (I don't control the DNS servers, so cannot change the TTL values to speed up the process). On my workstation, I added an entry in my HOSTS file for the new server, but used the IP address of the Apache server. So something like this:
192.168.0.15 www.newserver.com And the new server's IP is really 192.168.0.215. So now, when I force a refresh in the web browser for www.newserver.com, the HTTP request is sent to 192.168.0.15 and Apache handles it as a virtual host and redirects/proxies the request to 192.168.0.215. Just as real world traffic would be handled. So, I've been able to prove the virtual host and ProxyPass directives are working, but still need to handle the named virtual hosts on the IIS server. Right now I'm getting the default "No web site is configured at this address." message, so I know the virtual hosts on the IIS server isn't working. If I change my workstation's HOSTS file to use the actual server IP, The site(s) work as they should. But, this is an IIS problem now, not an Apache issue. Shawn On Friday 01 October 2004 11:59, Jamie Furtner wrote: > Investigate the ProxyPass / ProxyPassReverse directives. > > They're used to tell Apache that the resource /whatever is available at > http://10.1.1.1/whatever and has apache reverse-proxy the connection for > you. > > You could keep using virtual hosting on the IIS box, but it gets real > messy - it's best that you set up each site to a seperate address or > directory (address is better, in my mind) _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
