Open Bug 241816 Opened 21 years ago Updated 3 years ago

allow TYPE parameters in anchor tags to override server MIME types

Categories

(Core :: Networking, enhancement, P5)

enhancement

Tracking

()

People

(Reporter: kbriscoe, Unassigned)

Details

(Whiteboard: [necko-would-take])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040422 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040422 If a web server sends a (misconfigured) text/plain MIME type for a file, but the A HREF link to that file contains the correct MIME type, Mozilla should either 1) assume the A HREF type is correct, since someone went through the trouble of specifying it, or 2) prompt the user, because the web server and web page disagree on MIME type. My preference is 1, because the A HREF specified type can only be wrong if someone intentionally screws it up. Example: <a href="test.jar" type="application/java-archive"> on a default Apache/Linux web server, which returns text/plain for *.jar files. Currently Mozilla (1.7 PR1/Linux) opens this link inline as a text file. I think it should assume it's a Java archive and act accordingly. In a hosted environment web page authors may not have control over the server MIME types, and they may wish to use type="xxx" in cases where they know the server is wrong. This may also aid evangelism efforts. Reproducible: Always Steps to Reproduce:
Note that the HTML spec explicitly says that the server overrides the <a type>, so if we do this we should only do it for text/plain. Also note that currently the type from <a> is set as the type hint on the channel, so this would in fact have to be handled by necko...
Assignee: general → darin
Component: Browser-General → Networking: HTTP
QA Contact: general → core.networking.http
Summary: Mozilla should allow TYPE parameters in anchor tags to override server MIME types → allow TYPE parameters in anchor tags to override server MIME types
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This is still a bug as of 10/1/2005. See Boris' comments for what may need to be changed.
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
The type attribute "is purely advisory". Overriding the server is against the standard, making this either an Enhancement request or Invalid.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [necko-would-take]
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.