httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darrel Austin <daus...@visi.com>
Subject Re: Re-> help getting help - more specific.
Date Mon, 31 Dec 2001 19:04:53 GMT
Thanks Josh,

Yea, I figured it was more of an internet issue. What was interesting is how
many people couldn't figure this one out either. I had people offer all
sorts of interesting suggestions.

> Now, I'm not sure that an example like this really should be in the docs.
> If you don't really know what you are doing, you are just going to get
> yourself into trouble using this.

Agreed. 

Thanks for the tip, though. I may try getting myself into trouble this
week... ;)

-Darrel

on 12/31/01 1:02 PM, Joshua Slive at joshua@slive.ca wrote:

> 
>> From: Darrel Austin [mailto:daustin@visi.com]
> 
> 
>> The question was how do I run two physical servers (with VirtualHosts)
>> behind one IP address? I had assumed that it was a simple means of setting
>> up the VirtualHost configurations to see and direct requests to the other
>> server. Alas, after about a weeks worth of research and asking several
>> people who all offered suggestions that they THOUGHT would work, it became
>> apparent that there is no real way to do it via the VirtualHost.
> 
> This is not really a web server issue so much as a general internet issue.
> You can't, in general, have two machines with the same IP address, whether
> they are web servers or not.  The only exception is complicated
> load-balancing setups using fancy routers.
> 
> Having said that, it can actually be done by turning Apache into a fancy
> router.  I don't recommend this for a novice, but here goes:
> 
> NameVirtualHost *
> 
> <VirtualHost *>
> ServerName host1.example.com
> DocumentRoot /usr/local/apache/htdocs/
> </VirtualHost>
> 
> <VirtualHost *>
> ServerName host2.example.com
> ProxyPass / http://otherhost.example.com/
> ProxyPassReverse / http://otherhost.example.com/
> </VirtualHost>
> 
> Note that you need to have mod_proxy compiled into the server, and you need
> to be careful about how links on the backend otherhost.example.com server
> are constructed.  For more info, see the mod_proxy documentation.
> 
> Now, I'm not sure that an example like this really should be in the docs.
> If you don't really know what you are doing, you are just going to get
> yourself into trouble using this.
> 
> Joshua.
> 
> 
> ---------------------------------------------------------------------
> 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@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 


---------------------------------------------------------------------
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message