W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

allowing sniffed type list to be extensible? No.

From: Larry Masinter <masinter@adobe.com>
Date: Sun, 31 May 2009 10:26:22 -0700
To: Adam Barth <w3c@adambarth.com>, Anne van Kesteren <annevk@opera.com>
CC: Lisa Dusseault <lisa.dusseault@messagingarchitects.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <8B62A039C620904E92F1233570534C9B0118CD95EC7C@nambx04.corp.adobe.com>
On Mon, Apr 6, 2009 at 1:17 PM, Anne van Kesteren <annevk@opera.com> wrote:
> I sort of expect <video src> and <audio src> to do sniffing as well
> (ignoring Content-Type altogether most likely). @font-face ignores
> Content-Type as well because nobody had registered media types for fonts.

If content-type sniffing is context dependent -- @font-face sniffs font
types which img@src doesn't -- then the draft should be explicit about
that, rather than suggesting font sniffing for image sources.

There's no justification for allowing video@src or audio@src to be
sniffed. It just opens the door to more problems, and is not supported
by the justification of backward-compatibility with deployed content --
is there any other justification, besides someone "sort of expect"ing
it?

Larry
 
Received on Sunday, 31 May 2009 17:27:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:03 GMT