- From: Philip Jägenstedt <philipj@opera.com>
- Date: Tue, 20 Jul 2010 10:39:42 +0200
- To: public-html@w3.org
On Mon, 19 Jul 2010 17:33:14 +0200, Julian Reschke <julian.reschke@gmx.de> wrote: > Hi, > > <http://dev.w3.org/html5/spec/video.html#mime-types>: > >> The MIME type "application/octet-stream" with no parameters is never a >> type that the user agent knows it cannot render. User agents must treat >> that type as equivalent to the lack of any explicit Content-Type >> metadata when it is used to label a potential media resource. > > Can somebody explain the rational for treating application/octet-stream > the same way as absent media type information? > > Note, <http://greenbytes.de/tech/webdav/rfc2046.html#rfc.section.4.5.1>: > >> The recommended action for an implementation that receives an >> "application/octet-stream" entity is to simply offer to put the data in >> a file, with any Content-Transfer-Encoding undone, or perhaps to use it >> as input to a user-specified process. > > Best regards, Julian > Please don't fork a thread like this, especially not without linking to where it started: <http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027169.html> -- Philip Jägenstedt Core Developer Opera Software
Received on Tuesday, 20 July 2010 08:40:25 UTC