httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel-Stéphane SMORGRAV <>
Subject RE: [users@httpd] Re: Problems with proxying remote URLs
Date Mon, 29 Aug 2005 13:42:18 GMT
In Apache 1.3 I thought that was the case because what mod_rewrite actually does is prefixing
to the rewritten URL with proxy: when the [P] flag is appended to the rewrite rule. I may
be mistaken though, and 1.3 may use the same order as 2.0.

In Apache 2.0 mod_proxy is always run before mod_rewrite. That is why when you have a mix
of ProxyPass and RewriteRule ... [P] that conflict, the RewriteRule is never executed. When
that is the case, I use RewriteRules to do the proxying, and then add the ProxyPassReverse
as needed. Then mod_rewrite forces the request through the proxy module by setting some fields
in the request record object to apropriate values. SO although the proxy hooks are executed
before the rewrite hooks, the rewrite module apparently has a way to invoke mod_proxy...


-----Original Message-----
From: Jérôme Tytgat [] 
Sent: Monday, August 29, 2005 2:26 PM
Subject: Re: [users@httpd] Re: Problems with proxying remote URLs


How can you tell that mod_rewrite has to be executed BEFORE mod_proxy.

I would have used proxypass, but I can't because my rewrite are never reached and I need some
things to be rewritten BEFORE they are proxyfied.



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