We've been trying to reconcile various issues in config file Location
inheritance in httpd 2.2. In reading the core code, we've determined that
Locations truly are read and merged in order, and the most-specific (longest
Location strings) should go last. Therefore, we order our Locations in
increas
> Am I wrong? Is there some other reason why mod_proxy needs to go through the
> aliases in forward order, maybe related to regex matching?
Just convention that the first match is the operative one (which is
also why the "!" rules have to come before whatever would match them).
Could make it conf
Ah, I see. Iow, when you have proxypass or proxypassreverse directives in
server config, first match wins and per-directory merging works accordingly.
However, as in our case, when all proxypassreverse directives are instead
within Location tags, and it's always ProxyPassReverse / xxx, I don't s
Anyway, we'll file a bug report later in the week with an example config and
proposed solution. As it is now, there's no way to properly use
ProxyPassReverse in a directory scope when you use inherited settings in
nested Locations with other modules. The Locations need to be in
least-specific to mo
