> 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. Th
, August 29, 2005 2:26 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Re: Problems with proxying remote URLs
Ok.
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
Ok.
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.
Thanks.
J.
Axel-Stéphane SMORGRAV a écrit :
> In Apache 2.0 configurations
less thing
that can go wrong, therefore one less thing to consider when shit hits the fan.
-ascs
-Original Message-
From: Jérôme Tytgat [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 10:55 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Re: Problems with proxying r
> If memory serves me right, the modules added last are the ones executed
> first.
> You want mod_proxy to be executed after mod_rewrite so mod_rewrite must be
> loaded after mod_proxy.
Interesting point, I was facing that kind of problem when I wanted to do
rewrite rules plus
proxypass.
Wha
No reason to get cranky there.
My first thought also was that you are missing a proxy module. I understand you
are using Apache 1.3. What about the order in which the modules are loaded?
Could you try to rearrange them by putting the AddModule statement either at
the top or the bottom of the l
