DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39746>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39746 ------- Additional Comments From [EMAIL PROTECTED] 2007-09-07 10:22 ------- Nice to see that there comes a little bit of movement into this issue. We tried several things to get araound this bug but AllowEncodedSlashes will not solve the problem. As I wrote in my first post the failure occurs in mod_proxy. The mod_rewrite rule works perfectly - it translates the / characters into a %2F. If mod_proxy forwards this request afterwards it must definitly preserve the input url. As far as I understood the behaviour of mod_proxy it translates a % char into a %25 because it does not know that the original sequence is a %2F that should never be separated. So at last we have a %252F. This was never a problem at all as long as we had the third step that fixed the sequence back to %2F. But the apache fix 227435 will always eleminate step 3 if we have a reverse proxy. I guess there was a wise intention to build this fix but exactly for our szenario it will not work at all. So my colleagues are alwas forced to turn back the patch whenever they need a new apache version. Best regards. Markus -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
