Conventions, standards, or MIME type restrictions?

Given the new, proprietary file format that cannot currently be processed by any well-known application, I assume that you can simply come up with a new MIME value like this:

Content-Type: application/my-arbitrary-format 

Assuming this is the way, are there restrictions (format, syntax, length, reserved words or others), standards (IETF, ISO, W3C, IEEE, etc.), or conventions (like type/format slash)?

Please note that I do NOT want to use a known MIME value, because the browser and / or OS should not make assumptions about what may or may not open the file.

+4
source share
2 answers

To do this correctly, you can register your new type with IANA. http://www.iana.org/assignments/media-types/

+3
source

This page contains MIME type naming conventions. Here is a section on custom MIME types:

  • Use x. as a subtype prefix for experimental MIME types. Note that the x- prefix is ​​also valid for this purpose, but using x. not recommended x. to promote symmetry with other prefixes.

  • Use vnd. as a subtype prefix for MIME types for a particular vendor that are part of a commercial product. Vnd prefix vnd. must be accompanied by the name of the provider and a subtype separated by a period (for example, application/vnd.mozilla.xul+xml ).

  • Use prs. as a subtype prefix for personal / conceited MIME types that are not part of a commercial product.

+6
source

Source: https://habr.com/ru/post/1315093/


All Articles