httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 54158] New: Suggestion regarding 2.0 to 2.2 Upgrade Documentation and mod_proxy documentation
Date Fri, 16 Nov 2012 15:25:47 GMT

            Bug ID: 54158
           Summary: Suggestion regarding 2.0 to 2.2 Upgrade Documentation
                    and mod_proxy documentation
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Documentation
    Classification: Unclassified

Hello docs-project,
I have a suggestion regarding the 2.0 to 2.2 upgrade documentation, and the
mod_proxy documentation.  After upgrading we noticed a behavior change of
ProxyPass, specifically in how it works when used alongside RewriteRules.  In
2.0.64 we were able to mix them, and they appeared to be processed
sequentially.  However, in 2.2.23 it seems that RewriteRules are processed
first, and then the ProxyPass lines.  We came to this conclusion when we saw
our “catchall” rewrite rule at the bottom of our configuration getting
triggered before any ProxyPass requests.  We solved this by simply using
RewriteRules for everything.

I found enough in the documentation to indicate that this is an intended
behavior.  I found it by going to the documentation for mod_rewrite, then the
“more detailed mod_rewrite documentation”, and then finally “when not to use
mod_rewrite” which is here
 In the section on “Simple Proxying” after explaining ProxyPass, it has a note:

"You may need to use RewriteRule instead when there are other RewriteRules in
effect in the same scope, as a RewriteRule will usually take effect before a
ProxyPass, and so may preempt what you're trying to accomplish."

I could not find mention of this at all in the mod_proxy documentation at (which was my first stop in
trying to figure this out)... having the only mention of this need to use
mod_rewrite in a section titled "when *not* to use mod_rewrite" seems a bit

So my suggestion would be to include mention of this behavior change in the
upgrade documentation at
(provided that this is an intended behavior change), and possibly include the
same note quoted above in the mod_proxy documentation.

Thank you for your time,
-Henry S.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message