264848 - Implements moniker to automatically determine the content type

Status: RESOLVED INVALID

(Core :: Layout, enhancement)

Description

[zhsoft88]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20041018 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20041018 Firefox/0.9.3

In IE, when the server responses with mess contentType (text/plain or
application/octet-stream...), it uses moniker (FindMimeFromData) to determine
the most corrective contentType and renders the source by this contenttype, so
such pages as follows can be rendered as html text instead of html source:

http://www.sakal.co.il/
(https://bugzilla.mozilla.org/show_bug.cgi?id=257412)

http://www.bp.co.nz/local/index.shtml
(https://bugzilla.mozilla.org/show_bug.cgi?id=245299)

http://www.farmers.com/FarmComm/content/CC010116.JSP
(https://bugzilla.mozilla.org/show_bug.cgi?id=248300)

http://www.bible-prophecy.com/
(https://bugzilla.mozilla.org/show_bug.cgi?id=251938)

http://pgs.ruc.edu.cn/pages/zsxx.php3
(Firefox tells you to download file instead of renderring it)



Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[zhsoft88]

Attachment: patch

Comment 2

[zhsoft88]

This patch allow firefox to determine the contentType when the contentType is
ambiguous and use the most corrective contentType.

Comment 3

[Bill Mason]

First of all, this is not resolved fixed.  Unless you're saying you've checked
this patch into the code without anyone's review.

Second, this is not an issue to be 'fixed'.  If the server sends the wrong mime
type, that's a server problem.  Not a browser bug to be fixed.  The relevant
rules say that we should do just what we're doing: obeying the mime type sent by
the server.  That is already documented in several of the bugs you've linked to
here.

This is invalid.  Reopened to re-resolve it as such.