{
  "slug": "media-type",
  "term": "Media type",
  "aliases": [
    "MIME type",
    "Internet media type"
  ],
  "definition": "A media type identifies a data format and its intended processing model using a type, subtype and optional parameters.",
  "note": "Declaration: In HTTP, Content-Type carries a media type such as text/plain; charset=utf-8. Type and subtype names are case-insensitive; parameter values follow their own rules. A media type is distinct from a filename extension or a content encoding such as gzip. Distinct media types may share the same data format while specifying different processing models; inspecting bytes alone cannot always recover the intended interpretation. [http-media-type]\n\nStored metadata: S3 exposes Content-Type as user-controlled system metadata. It is not a checksum or a result of validating every byte of an object. Retain the interpretation metadata alongside the selected bytes. A version selector and metadata validation answer separate questions. [s3-content-type]\n\nIdentification: Magic bytes and filename extensions are separate clues to a media type. A matching signature does not establish that the remaining file satisfies the format. HTTP content sniffing can also select an unintended processing model. [media-registration] [http-media-type]\n\nResponse boundaries: Content-Type is a singleton, not a comma-separated list; conflicting copies can produce different recipient interpretations. [http-media-type] Barth, Caballero and Song's 2009 study showed how upload filters and then-current browser sniffers could assign incompatible types to the same file. This is historical evidence, not a claim that current browsers retain those attacks. [sniffing-2009]",
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-22",
  "related": [
    "file-signature",
    "object-storage",
    "data-serialization",
    "character-encoding"
  ],
  "citations": [
    {
      "id": "http-media-type",
      "title": "RFC 9110: Content-Type and media types, sections 8.3 and 8.3.1",
      "url": "https://www.rfc-editor.org/rfc/rfc9110.html#section-8.3",
      "accessed": "2026-11-22"
    },
    {
      "id": "media-registration",
      "title": "RFC 6838: additional media-type identification information, section 4.12",
      "url": "https://www.rfc-editor.org/rfc/rfc6838.html#section-4.12",
      "accessed": "2026-11-22"
    },
    {
      "id": "s3-content-type",
      "title": "Amazon S3: system-defined object metadata",
      "url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html#SysMetadata",
      "accessed": "2026-11-22"
    },
    {
      "id": "sniffing-2009",
      "title": "Barth, Caballero and Song (IEEE S&P 2009): content sniffing, sections 2.3-3.4",
      "url": "https://bitblaze.cs.berkeley.edu/papers/mimesniff_oakland09.pdf",
      "accessed": "2026-11-22"
    },
    {
      "id": "hesela-context",
      "title": "Hesela: identify the format, then validate the file",
      "url": "https://hesela.com/analyses/object-etags-checksums-conditional-writes/#format-identification",
      "accessed": "2026-11-22"
    }
  ],
  "provenance": [
    "Primary-source terminology for HTTP and stored-object interpretation; no live object-store experiment or browser security evaluation."
  ]
}
