Krist,
Ignore my last question, I was missing a quote. Thanks a bunch, that did it.
My final rule looks like:
RewriteCond %{REMOTE_HOST} ^192\.168\.220\.
RewriteRule "^(/.*)$" "proxy:balancer://aquabrowser$1?c_loc=220" [QSA,L]
Krist van Besien wrote:
> On Feb 11, 2008 3:25 PM, Travis Si
Thanks, I see what's going on now.
Here is what I've tried followed by the response on the backend server:
Case 1:
RewriteRule "^/(.*)$" proxy:balancer://aquabrowser$1?c_loc=220" [QSA,L]
"GET /?c_loc=220\" HTTP/1.1" -> Note I get a 500 error when trying to access
anything other then /.
Case2:
On Feb 11, 2008 3:25 PM, Travis Sidelinger <[EMAIL PROTECTED]> wrote:
>RewriteRule "^/(.*)$" proxy:balancer://aquabrowser$1&c_loc=220" [QSA,L]
> # I
> get 404 Error: "GET //cd/README&c_loc=220%22?test=1 HTTP/1.1" in the logs of
> the
> backend server.
You append "&c_loc=220" to the URL, a
I see that now. Will check with the developers and see if they can work with
that. Thou, I'd still like to know why mod_rewrite is behaving funny.
Mike Cardwell wrote:
> mod_proxy should add an extra HTTP header to the request called
> "X-Forwarded-For" which you can parse to retrieve the IP add
mod_proxy should add an extra HTTP header to the request called
"X-Forwarded-For" which you can parse to retrieve the IP address from.
Note, this can contain multiple IPs if there are several proxies on
route so make sure you parse it correctly.
Regards,
Mike
Travis Sidelinger wrote:
We have
We have used both mod_rewrite and mod_proxy successfully in numerous
configurations. Put them together and they don't seem to like each other.
We have a working production mod_proxy_balancer configuration for two backend
web servers that is working great, except... The backend web servers need t
