- From: Maciej Stachowiak <mjs@apple.com>
- Date: Mon, 19 Jul 2010 11:09:46 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, "public-html@w3.org" <public-html@w3.org>
On Jul 19, 2010, at 8:54 AM, Julian Reschke wrote: > On 19.07.2010 17:41, Boris Zbarsky wrote: >> On 7/19/10 11:33 AM, Julian Reschke wrote: >>> Can somebody explain the rational for treating application/octet-stream >>> the same way as absent media type information? >> >> Well, for one thing this is a common web server misconfiguration >> (default configuration in IIS, last I checked). > > Chicken and egg. > > I can see this for legacy types, but we are defining a new feature here. > > If no UA plays application/octet-stream, then the risk of people serving video without proper type is zero. For Safari/WebKit, we wanted to make it possible for the <video> element to play content that was previously embedded via the QuickTime plugin or other plugins we support. Unfortunately, a fair proportion of such content is being served with the wrong MIME type, most typically application/octet-stream but sometimes also text/plain. We thought it might create too high a barrier, if authors had to reconfigure their Web servers before they could switch from the QuickTime plugin to <video>. Regards, Maciej
Received on Monday, 19 July 2010 18:10:21 UTC