This is actually an Apache problem when it's trying to redirect the browser to the new address, it gets the server name wrong because it is trying to use the private address... Here's the option you need to look at in httpd.conf:
# ServerName allows you to set a host name which is sent back to clients for # your server if it's different than the one the program would get (i.e., use # "www" instead of the host's real name). # # Note: You cannot just invent host names and hope they work. The name you # define here must be a valid DNS name for your host. If you don't understand # this, ask your network administrator. # If your host doesn't have a registered DNS name, enter its IP address here. # You will have to access it by its address (e.g., http://123.45.67.89/) # anyway, and this will make redirections work in a sensible way. # # 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your # machine always knows itself by this address. If you use Apache strictly for # local testing and development, you may use 127.0.0.1 as the server name. # #ServerName new.host.name You will likely want to set ServerName to your firewall's IP address. -- Jim Pingle At 11:24 AM 5/15/2002 -0700, you wrote: > I'm having issues with my exposed (RDR'ed) website. The subdirectories > do not work without trailing slashes, it does not reidrect the clients > to the correct path. It works fine without the firewall in the middle. > eg: > > http://mydomain.com/mydir -- doesn't work from behind the firewall. > http://mydomain.com/mydir/ - works just fine. > > I figured that the server was having issues sending redirects to the > browser so I added the second line to the NAT rules. > > Here are the rules for the site: > > rdr fxp1 66..x.y.z/32 port 80 -> 10.x.x.x port 8090 tcp > map fxp1 from 10.x.x.x/32 port = 8090 to any -> 66.x.y.z/32 > > Pass in log quick on fxp1 proto tcp from any to 10.x.x.x/32 port = 8090 > flags S keep state > > Any ideas anyone? > > TIA.
