httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Cocker" <>
Subject RE: [users@httpd] Redirecting to internal server
Date Tue, 27 Nov 2007 08:25:41 GMT
Thanks for that, I'll give it a try. Looks a lot easier :)

Out of interest, what is the example below doing? The document
referenced doesn't exist on the box in question, it is on an internal
box, and the external facing box has a route in its routing table
specifically for the internal box.

So, in some way it's deciding to pass requests in, and the below is the
only uncommented reference to that box in all of httpd.conf. So either:

a) I'm looking in the wrong file for the relevant interaction.

b) Uh... something else :)
All I know is that must be
passed through somehow (indeed, the DMZ/Internal router has a whole NAT
config for it), since page.html exists only on the internal server, not
the external facing www one.

Paul Cocker 
IT Systems Administrator 
IT Security Officer 

01628 81(6647) 

TNT Post 
1 Globeside Business Park 
Fieldhouse Lane 
SL7 1HY 



From: Victor Trac [] 
Sent: 24 November 2007 11:13
Subject: Re: [users@httpd] Redirecting to internal server

On Nov 23, 2007 6:52 PM, Paul Cocker <> wrote:

	Hi all, first time on the apache list so have mercy ;)
	I have been tasked with setting up a system whereby a Linux
	running apache 2.0.59 in the DMZ takes requests on port 80 and
	passes them through to an internal Windows server running IIS
	actually hosts the HTML.
	Such a setup already exists (though it's Linux to Linux) so I
	this would be relatively easy to do, just copy the existing
	People currently connect to
	and all is well. Searching the httpd.conf file I can find only
	reference to folder, which is:
	<VirtualHost *:80>
	    DocumentRoot /var/www/html/domain
	    RewriteEngine on
	    RewriteRule ^/folder(.+)$1 [R,L]
	    RewriteRule .* - [F]
	So we're using the rewrite module... except having read the 
	documentation on this feature I cannot fathom it.
	I hoped that with the above I could simply add another line:
	RewriteRule ^/folder2(.+)$1
	I then added a route for the relevant server so the traffic is
routed to
	the internal network when its name is called. However, without
	understanding the above I'm not in much of a position to
	further when this invariably fails to work. I don't know whether
	above in any way relates to the name apache calls which then
causes the
	call to be routed to server X.
	Any advice or guidance you can offer would be much appreciated. 
	Paul Cocker
	IT Systems Administrator <> 

Your example is not rewriting to an internal server.  You want to use
mod_proxy.  Let's say your windows box is, then you want
something like this inside your VirtualHost directive:

ProxyRequests off
ProxyPass /folder2
ProxyPassReverse /folder2

With this, anytime someone visits your externally accessible site at, they'll see the html output by your
windows server at and your internal IIS host is
never directly accessible from the internet. 



TNT Post is the trading name for TNT Post UK Ltd (company number: 04417047), TNT Post (Doordrop
Media) Ltd (00613278), TNT Post Scotland Ltd (05695897),TNT Post North Ltd (05701709) and
TNT Post South West Ltd (05983401). Emma's Diary and Lifecycle are trading names for Lifecycle
Marketing (Mother and Baby) Ltd (02556692). All companies are registered in England and Wales;
registered address: 1 Globeside Business Park, Fieldhouse Lane, Marlow, Buckinghamshire, SL7

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