It would be good to know why you want to serve TypeScript files. As far as I understand, TypeScript is used to compile to Javascript, which is then executed in a browser. Currently, there is no native support for TypeScript (correct me if I’m wrong). If you still want to serve .ts files via IIS, … Read more
Make use of the finfo() functions. A simple illustration: <?php $finfo = finfo_open(FILEINFO_MIME_TYPE); echo finfo_file($finfo, “path/to/image_dir/image.gif”); finfo_close($finfo); OUTPUT : image/gif Note : Windows users must include the bundled php_fileinfo.dll DLL file in php.ini to enable this extension.
As I have decided to follow the jsonapi.org standard, I decided to do just what your example shows. Regarding your questions: Your MIME type should be registered I believe that each version and type should be registered, as they are unique types x- prefix has been deprecated as noted in a comment application/json-v2 would not … Read more
Google Docs: application/vnd.google-apps.document application/vnd.google-apps.kix Google Presentations: application/vnd.google-apps.presentation Google Spreadsheets: application/vnd.google-apps.spreadsheet Google Drawing: application/vnd.google-apps.drawing See here for more information. Here is a long list of Google Docs and Google Drive MIME types (it is not exhaustive): application/vnd.google-apps.audio application/vnd.google-apps.document application/vnd.google-apps.drawing application/vnd.google-apps.file application/vnd.google-apps.folder application/vnd.google-apps.form application/vnd.google-apps.fusiontable application/vnd.google-apps.kix application/vnd.google-apps.photo application/vnd.google-apps.presentation application/vnd.google-apps.script application/vnd.google-apps.sites application/vnd.google-apps.spreadsheet application/vnd.google-apps.unknown application/vnd.google-apps.video
http://www.iana.org/assignments/media-types/ lists the “official” mime-types, but it doesn’t prevent anyone making their own an not registering it with IANA.
There’s an expired IETF proposal that suggests application/protobuf. It does not address the question how the receiving side could determine the particular message type. Previous discussions suggested using a parameter to specify package and message, e.g. application/protobuf; proto=org.some.Message In practice, the types you listed seem to be indeed the ones in use, for example the … Read more
tl;dr: text/markdown since March 2016 In March 2016, text/markdown was registered as RFC7763 at IETF. Previously, it should have been text/x-markdown. The text below describes the situation before March 2016, when RFC7763 was still a draft. There is no official recommendation on Gruber’s definition, but the topic was discussed quite heavily on the official mailing-list, … Read more
vnd indicates vendor-specific MIME types, which means they are MIME types that were introduced by corporate bodies rather than e.g. an Internet consortium.
I’d recommend application/octet-stream as RFC2046 says “The “octet-stream” subtype is used to indicate that a body contains arbitrary binary data” and “The recommended action for an implementation that receives an “application/octet-stream” entity is to simply offer to put the data in a file[…]”. I think that way you will get better handling from arbitrary programs, … Read more