>Number: 5687 >Category: general >Synopsis: unexpected behavior when '%2f' in path-info >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Feb 02 12:20:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: [EMAIL PROTECTED] >Release: 1.3.9 >Organization: apache >Environment: Sun Solaris, SunOS somesun 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-1, gcc 2.8.1 >Description: Using additional characters - including slashes - behind a script or document in a URL puts them into PATH_INFO, which is fine. I was quite surprised to see apache misinterpret the base64-encoding (%2f") of the slash character for a real slash, ending up in a 404.
Just in case this is not a feature, I thought I'd let somebody know. >How-To-Repeat: http://www.apache.org/index.html/test/test => 200 http://www.apache.org/index.html/test%2ftest => 404 >Fix: Quickfix: mod_rewrite. Realfix: revisit url/path encoding/handling >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
