Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 5 Feb 2003 23:57:21 -0000
Message-ID: <20030205235721.28998.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 16368]  -
    LoadModule order for mod_proxy and mod_rewrite

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16368>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16368

LoadModule order for mod_proxy and mod_rewrite

nd@perlig.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Minor                       |Normal
             Status|NEW                         |ASSIGNED
            Version|2.0.43                      |HEAD


------- Additional Comments From nd@perlig.de  2003-02-05 23:57 -------
hmm, it looks like the fixup hooks of mod_rewrite and mod_proxy create the
problem (both HOOK_FIRST).

first case:
mod_rewrite runs first: create r->filename=proxy:http://foo/bar?baz
mod_proxy runs afterwards: enode that url and append query (again):
http://foo/bar%3Fbaz?baz
-> proxy handler runs with the result

second case:
mod_proxy fixup runs empty (no proxy request)
mod_rewrite creates r->filename=proxy:http://foo/bar?baz
-> proxy handler runs with the result.

We can solve this for now by hooking mod_proxy fixup explicitely before
mod_rewrite. But AFAICS we need some further research to handle all the proxy
stuff more clean.

Opinions?

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org