DO NOT REPLY [Bug 20372] New: - AllowEncodedSlashes doesn't work with reverse proxy

[bu...@apache.org]

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=20372>.
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=20372

AllowEncodedSlashes doesn't work with reverse proxy

           Summary: AllowEncodedSlashes doesn't work with reverse proxy
           Product: Apache httpd-2.0
           Version: 2.0.46
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: ftrentini@uolinc.com


The new directive AllowEncodedSlashes doesn't work using apache 2.0.46 as a 
reverse proxy configuration, look at the example below:

bash-2.05a# grep AllowEncodedSlashes httpd.conf
AllowEncodedSlashes On

bash-2.05a# grep "returning 404" errorlog_80 |tail -1
[Fri May 30 17:58:56 2003] [info] [client x.x.x.x] found %2f (encoded '/') in 
URI (decoded='/blahblah'), returning 404, referer: http://blahblah.com


I'm using something like this:
    RewriteEngine   on
    RewriteRule     ^(.*)$     $1 [P,L]


Thanks in advance, 
Fabio.

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