httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Balabalame" <>
Subject Re: [users@httpd] mod_proxy report "DNS lookup failure" when combined mod_proxy and mod_rewrite
Date Sat, 23 Feb 2008 08:56:52 GMT
Thanks for your suggestion, Joshua.

Yes, the rule RewriteRule ^/balancer-manager$ /balancer-manager [P,L] makes
no sense. I just pick it as an example.

In fact, my rule is like "RewriteRule ^/(.*) /%{ HTTP_REFERER}/$1 [P,L]".
But Apache also returns 502 error. So I simplify my rule to "RewriteRule
^/balancer-manager$ /balancer-manager [P,L]" to confirm that the rule itself
has no error and the error must occured inside Apache itself.

According to the rewrite log, I found the the url passed to mod_proxy( is correct. And that why
mod_proxy can not return the right result is what I am confused.

Any suggestion? Thanks.


On Fri, Feb 22, 2008 at 4:27 AM, Joshua Slive <> wrote:

> 2008/2/20 Robert Balabalame <>:
> >
> >     ProxyPass /balancer-manager !
> >     RewriteEngine On
> >     RewriteRule ^/balancer-manager$ /balancer-manager [P,L]
> >  Reason: DNS lookup failure for:
> > But I can access successfully if
> I
> > delete the line that contains "RewriteRule ..."
> It seems like "DNS lookup failure" may be a red herring. But that
> RewriteRule makes no sense. What is it supposed to do? It is proxying
> a request back onto itself, which should create an infinite loop.
> I don't think you even need that line at all, given that you have the
> ProxyPass line above that cancels proxying for that URL. If you need
> to cancel some other rewriting, you can use
> RewriteRule ^/balancer-manager$ - [L]
> Joshua.
> ---------------------------------------------------------------------
> 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