You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/12/13 20:35:44 UTC

DO NOT REPLY [Bug 25501] New: - wrong extension handling

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

wrong extension handling

           Summary: wrong extension handling
           Product: Apache httpd-1.3
           Version: 1.3.29
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: carramba@pf.pl


if there exists file
xxx.gif.xyz
on server's location
and we do simple http/1.1 transaction:
GET /xxx.gif HTTP/1.1
Host: xxxxxxxxxxx

we get:
HTTP/1.1 200 OK
Date: Sat, 13 Dec 2003 19:27:24 GMT
Server: Apache/1.3.26 (Unix) Debian GNU/Linux mod_ssl/2.8.9 OpenSSL/0.9.6g
PHP/4.1.2 [example]
Content-Location: xxx.gif.xyz
Vary: negotiate
TCN: choice
Last-Modified: Sat, 13 Dec 2003 19:27:05 GMT
ETag: "9ba-0-3fdb6809;3fdb6809"
Accept-Ranges: bytes
Content-Length: 0
Content-Type: chemical/x-xyz

Yes, we get Content-Location header, but there's no requested file on webserver,
so shouldn't we return 4xx response?

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