DO NOT REPLY [Bug 16595] New: - server-parsed documents served with "/xxx" added to correct URL

[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=16595>.
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=16595

server-parsed documents served with "/xxx" added to correct URL

           Summary: server-parsed documents served with "/xxx" added to
                    correct URL
           Product: Apache httpd-1.3
           Version: 1.3.26
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_include
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: dbaron@dbaron.org


Documents using the server-parsed handler are incorrectly served (instead of
giving a 404 error) when the URL for the server-parsed page has a / appended to
it, perhaps followed by additional characters.  This is a problem mainly because
it serves the document in a form that breaks relative URLs and server-side includes.

Steps to reproduce:
 Create an .htaccess file with:
    AddType "text/html; charset=iso-8859-1" .abug
    AddHandler server-parsed .abug
 and create a simple foo.abug file in that directory.

Actual results:
  http://server/dir/foo.abug , http://server/dir/foo.abug/ , and
  http://server/dir/foo.abug/bar all return the document.

Expected results:
  Only the first of the three URLs should return the document.

This bug can be seen on a live server (which uses "Options +MultiViews") at:
  http://dbaron.org/log/2003-01
  http://dbaron.org/log/2003-01/
  http://dbaron.org/log/2003-01/aaaa

(Users of my pages are occasionally confused by the fact that I use MultiViews
and don't use extensions in my URLs.  This is, after all, good practice:
http://www.w3.org/Provider/Style/URI.html .  However, occasionally users think
the URL is a directory, since it lacks an extension, and add a slash to the end.
 This problem has been pointed out to me a number of times over the past few
years, so I'm finally breaking down and filing a bug despite not having tested
it on the very latest version of Apache (or on Apache 2.0, for that matter),
since I'm not running my own server and don't have the time to set one up just
to test this bug.)

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