httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21727] New: - Redirect directive doesn't work if content negotiation involved
Date Sat, 19 Jul 2003 13:33:43 GMT
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=21727>.
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=21727

Redirect directive doesn't work if content negotiation involved

           Summary: Redirect directive doesn't work if content negotiation
                    involved
           Product: Apache httpd-2.0
           Version: 2.0.45
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: mod_alias
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: st@kino-fahrplan.de


Following in .htaccess:

  Redirect gone /test
  Options +multiviews

If there exists a file like /test.html it will be served upon a request for
/test instead of the intended "410 gone". If the file is renamed to /test you'll
get the 410.
This happens with any type of redirect, not just 410 in the example above.

The mod_alias/Redirect docs clearly say that "the Redirect directive maps an old
URL into a new one", so it is supposed to work on URLs, those things coming from
the client, not the file paths or URLs they resolve to internally.

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


Mime
View raw message