Maybe try this:
RewriteRule ^(.*)$ http://unique.host.com:8000/$1?ip=%{REMOTE_ADDR}
[P]
or
RewriteRule ^(.*)$
http://unique.host.com:8000/index.php?request=$1&ip=%{REMOTE_ADDR} [P]
with a rewrite rule on the receiving server to bring it back to the
original request.
You probably want something like mod_perl or php to handle this most
effectively
(i.e. for doing something with the IP addy, etc. )
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
On Jan 30, 2006, at 1:12 PM, allan juul wrote:
hello,
we have on the same machine an apache2 in front (80) of a backend web
server (8000) in a reverse proxy set up. the backend sees the proxied
requests from the apache as coming from localhost.
we are in a situation were we need the backend to see the request
coming
from anything but localhost.
one approach might be to establish a unique host header on the backend,
so the apache would forward requests like:
RewriteRule ^/(.*) http://unique.host.com:8000/$1 [p,l]
instead of
RewriteRule ^/(.*) http://localhost:8000/$1 [p,l]
i just wander if there are an easier / or even another solution to
this?
perhaps forwarding the original client ip somehow.
thanks
./a
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
