This is primarily a misunderstanding of how clients (not the server) deals
with HTML tags.
Basically the client is being redirected correctly to the port you
specified... but this port in turn is non-standard.
The hrefs however do not return the information about the redirected
machine, rather they point to a "generic" html address. Since no port number
is specified on this link the CLIENT looks up the wrong machine. That is it
looks up a reference to a "normal" html tag not a remapped one.
You'll have to modify ALL of your tags to reflect your non-standard port
mappings OR you have to inwardly redirect all html access into the target
machine. In effect the target machine becomes the server for http accesses
coming in from outside, and then use standard port ID's.
This would limit you to this one redirected machine as a web server... but
it would solve your problem by eliminating the use of your :9000 port
scheme.
I know of no way around this. This is NOT an apache or web server problem...
remember the link is basically telling the client, "ok now access THIS
link ->>> http://www.filename.html" instead of "ok now access this link ->>>
http://www.filename.html:9000". The value of the link is returned to the
client (not the server) and the client then queries for the new link as if
performing a NEW page search.
-JMS
-----Original Message-----
From: Jeremy Hansen <[EMAIL PROTECTED]>
To: Linux Servers mailing list <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, October 16, 1998 11:19 AM
Subject: Re: Question about webserver proxies and internal networks.
>
>Ok, I've been trying to use redir now, but I'm running into another
>problem and I suspect that it's Apache's fault and not the redirector.
>
>real.machine.com:9000 => internal.machine.com:80
>
>The index page that exists on internal.machine.com:80 has some links to
>specific mrtg devices. These links are just local file pointers, you know
><a href="filename.html">. Well for some reason that I can't figure out,
>when I click on one of links on the index.html page through
>real.machine.com:9000, the web server tries to contact real.machine.com
>and not real.machine.com:9000 therefore screwing everything up. What
>really boggles my mind is the clients seems to recognize the url and port
>in the link. When I point to the link, that Netscape status says:
>
>http://real.machine.com:9000/filename.html
>
>I hope that wasn't confusing.
>
>
