Re: Apache VirtualHost to another machine

["Brad Alpert" <BAlpert FortBradford com>]

Downleveling to Apache 1.3 isn't the direction I want to go, though.

I've tried ProxyPass and ProxyPassReverse (having, of course, loaded
mod_proxy into httpd.conf) and the result is that the external http
query to the FQDN of my internal machine's winds up serving the
main, outside server's pages.

>From my reading (and I could be way wrong about this), ProxyPass
seems designed to redirect specific directories, and what I want to
do is to make an entire website on another machine appear.

I will take a look at Squid; hadn't thought of that as a solution.

As to the reason, the main one is that I don't want to load one
machine up with websites when it's already running lots of other
things.  Plus, I am trying to learn this stuff.  And, as I noted
earlier, I used to run IIS and I want to be able to do everything
that I could do with it and more.

Thanks for the reply.

Brad

>> This has to be doable in apache..  I can't believe there aren't
>> people out there on apache running any number of internal
>> virtual servers, addressable by unique domain name, from a
>> single IP.
>
> ProxyPass works just fine for this, although you may have to use
> Apache 1.3 (In Apache 2 I've found that although ProxyPass is
> documented as a per-virtual-host config, it actually works as a
> server-wide config).
>
> Another possible solution is to use SQUID.
>
> Of course, one has to ask, what's the purpose, anyway?  Why not
> just mount the files off of the inside computer and run them all
> from the outside computer?
>
> Jon