W3C home > Mailing lists > Public > public-html-wg-issue-tracking@w3.org > February 2010

ISSUE-104 (sniffing-optional): Clarify that mime type sniffing is optional [HTML 5 spec]

From: HTML Weekly Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 18 Feb 2010 15:02:27 +0000 (GMT)
To: public-html-wg-issue-tracking@w3.org
Message-Id: <20100218150227.67F077F408@otto.w3.org>

ISSUE-104 (sniffing-optional): Clarify that mime type sniffing is optional [HTML 5 spec]


Raised by: Julian Reschke
On product: HTML 5 spec

Escalated from: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7744

The spec currently delegates this issue to the MINESNIFF spec.

Problems with that:

- that spec is a moving target and currently has no owner except the author (it's an Internet Draft without WG nor with a clear plan how to proceed)

- it's unnecessarily complicated to find out whether sniffing is required or not 

- the links in HTML5 aren't particularly helpful because they just point to the MIMESNIFF spec in total, not particular sections

Repeating the link five times without any annotation also doesn't help (see http://www.w3.org/Bugs/Public/show_bug.cgi?id=7744#c22)

Larry Masinter has made a proposal for changed text in http://www.w3.org/Bugs/Public/show_bug.cgi?id=7744#c25:

"The Content-Type metadata of the result of fetching a representation from a
resource depends on the URI scheme and corresponding protocol. However, there
are some circumstances where additional heuristics (overriding the protocol
defaults) are needed for compatibility with current web sites.  Guidelines for
determining an appropriate content-type to presume are being developed
elsewhere [MIMESNIFF]; in particular, user agents MUST NOT use additional
heuristics or override authoritative metadata in ways that are not explicitly

HTML5-SPEC-SECTIONS [content-type-sniffing]
Received on Thursday, 18 February 2010 15:02:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:50:24 UTC