User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Opening the url http://www.rockbox.org/irc/rockbox-20050527.txt pops up Firefox'
download-dialog even though the webserving is specifying the mimetype
text/plain. The file includes 6 non-printable characters, but I don't believe
this warrants ignoring the mimetype specified by the server.
Steps to Reproduce:
1. Open url http://www.rockbox.org/irc/rockbox-20050527.txt
2. That's it
3. There is no 3.
Firefox opens its "Save or open with" dialog.
Display the file-contents as text/plain as the server specified.
Same for Moz 1.7.8. I guess this is because the txt file contains some special
characters (non-printable) and the parser decides not to display it (thinks this
is some of the binary file types which are sent wrongly with plain/text).
Mozilla auto-sniffing decided that this can't be text. You can see that at the
text of the save as dialog in recent Mozilla trunk builds.
I think this is an edge case and will probably not fixed but confirming because
the developers must decide what to do with this bug report...
GET /irc/rockbox-20050527.txt HTTP/1.1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
HTTP/1.x 206 Partial Content
Date: Sat, 28 May 2005 05:35:05 GMT
Server: Apache/2.0.54 (Debian GNU/Linux) PHP/4.3.10-12
Last-Modified: Fri, 27 May 2005 21:59:02 GMT
Content-Range: bytes 45260-75217/75218
Keep-Alive: timeout=15, max=99
Content-Type: text/plain; charset=iso-8859-1
Could firefox be leaving it up to the user what to do since it believes that the
page is possibly corrupted (partial content)?
> Server: Apache/2.0.54 (Debian GNU/Linux) PHP/4.3.10-12
This is a known-buggy server that sends "text/plain; charset=iso-8859-1" for any
content it doesn't recognize. We've been forced to work around such servers
after asking them for years to fix the bug. See
http://issues.apache.org/bugzilla/show_bug.cgi?id=14095 for the discussion on
the Apache bugs.
Note, further, that sending the document in question as text/plain is in fact a
violation of the RFC that defines the text/plain MIME type, since the file
_does_ include said unprintable characters (which text/plain files are not
allowed to do).