httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Byers <>
Subject [users@httpd] How to configure Apache 2.2.8 to act as reverse proxy?
Date Wed, 14 Oct 2009 21:28:57 GMT

This ought to be a FAQ, but I haven't found it yet.

Please be patient with my as I am out of my element (I develop software, and
I don't normally administer servers of any sort).  I need a simple set up so
I can write and test code that handles the VIA HTTP header.

If I've understood the documentation I've found so far, this would be a
reverse proxy.

The server on which this would be most useful is running IndigoPerl.  Alas,
the examples I found so far for configuring a proxy refer to modules not
shipped in the Indigoperl distribution.  I do not have a set up where I can
build Apache, and don't want to build it if I can avoid it.  It has several
proxy modules (,,, &c.) but
apparently not the ones that rewrite links to pages on the httpd server that
is hidden from the outside world by the firewall.

I have two machines with non-routable IP addresses behind a firewall.  The
router is configured to send requests on port 80 to one of the two machines. 
I have a fixed IP address from my ISP, but I do not have a domain name.

Let's say my two machines have the IP addresses and,
and the latter has my fixed IP address: x1.x2.x3.x4.  How do I tell the
apache server on the latter that requests come in to x1.x2.x3.x4 are to be
served from the local htdocs directory and that those coming in on
x1.x2.x3.x4/the_other_website are to be obtained from  That is
x1.x2.x3.x4/the_other_website/cgi-bin maps to (and that
any links on any page on either machine of the form
are handled correctly rather than giving the user an error message).

I have found that a link like on a page in works fine when logged on to, but it gives an
error from a machine outside the LAN indicating the page doesn't exist (and
I know that is because there is no such IP address in the LAN that includes
the machine I used to test this).

Can you please provide me with an URL that tells me the absolute minimum, in
terms of modules and directives in the configuration file, to get this
working so I can get on with writing the code to process the VIA HTTP
headers?  Or failing that, tell me the bare minimum I need in modules and
directives, to get this working?


View this message in context:
Sent from the Apache HTTP Server - Users mailing list archive at

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message