W3C home > Mailing lists > Public > public-html@w3.org > July 2010

video/@src vs application/octet-stream

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 19 Jul 2010 17:33:14 +0200
Message-ID: <4C44703A.4070406@gmx.de>
To: "public-html@w3.org" <public-html@w3.org>


> 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
Received on Monday, 19 July 2010 15:33:48 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:21 UTC