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 Summary: LoadModule order for mod_proxy and mod_rewrite Product: Apache httpd-2.0 Version: 2.0.43 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: Other Component: mod_rewrite AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] It seems that some strange side effects happen if mod_rewrite is loaded before mod_proxy. I have the following in the httpd.conf: --- snip --- LoadModule rewrite_module modules/mod_rewrite.so LoadModule proxy_module modules/mod_proxy.so --- snap --- and the following in an .htaccess (cgi-perl/.htaccess): --- snip --- RewriteEngine On RewriteRule (.*) http://192.168.111.111:8080/no/$1 [P] --- snap --- which produces an unexptected result for the request: http://127.0.0.1/cgi-perl/blah?world=reboot . It sends an request http://192.168.111.111:8080/no/blah%3Fworld=reboot?world=reboot . The the two LoadModule lines are exchanged so that mod_proxy is before mod_rewrite it works as expcted (request http://192.168.111.111:8080/no/blah?world=reboot is sent). I don't know if this is really an bug or intended (I see it a bit as bug). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
