[users@httpd] Mod_proxy definitions taking precedence over mod-rewrite rules (Again)

["Kevin D. Van Der Hart" <kv...@vermeermfg.com>]

I sent this message once but received no responses and have not been
able to resolve the problem. Any ideas would be highly appreciated.

I am running Apache 2.0.55 on Solaris. I have some mod-rewrite rules
that had been working properly that make changes to URLs that also would
be valid under some mod_proxy settings on a specific name based virtual
host. Mod_rewrite is compiled into httpd and mod_proxy is loaded as a
DSO. I upgraded the Solaris OS from 8 to 10 and now the proxy rules are
taking priority over the mod_rewrite rules and my rewrites are failing.
I have some rewrite rules that don't conflict with mod_proxy rules and
they work as expected so I know both modules are loaded and working
properly. With Apache 1.X I specifically loaded modules in a set order
so mod_rewrite would have precedence over mod_proxy. Can this be done
with Apache 2.0? I tried recompiling Apache on the new OS but that had
no effect.

Thanks.

Kevin

---------------------------------------------------------------------
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: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org