Media type / audio
audio/midi
MIDI sequences: performance instructions rather than recorded sound, so files are tiny.
Served inline: Browsers have no renderer for this, so it downloads even without a Content-Disposition header. That makes it the quiet default for anything you do not want opened in place.
Browser behaviour
Downloads
Charset
no charset
Compression
Compress in transit
Send it like this
Content-Type: audio/midiA binary payload has no character encoding. A charset parameter here is meaningless and occasionally confuses strict parsers.
Handling verdict
Browsers have no renderer for this, so it downloads even without a Content-Disposition header. That makes it the quiet default for anything you do not want opened in place.
A binary payload has no character encoding. A charset parameter here is meaningless and occasionally confuses strict parsers.
The payload is text-like or otherwise repetitive, so gzip or Brotli removes real bytes. Enable it at the server or CDN.
Registered with IANA through a public review process, so the name is stable and every implementation can rely on it meaning the same thing.
Anatomy of the name
RFC 6838Top-level type
audio
Audio
Subtype
midi
Registered in the standards tree.
Structured syntax
none
No suffix, so the payload format is defined entirely by the subtype itself.
Parameters
none
Beyond the charset rule above, this type defines no parameters of its own.
Response headers
Content-Type: audio/midi
X-Content-Type-Options: nosniff
Content-Disposition: attachment; filename="example.mid"
Vary: Accept-Encodingnosniff stops the browser second-guessing the type you declared, which is what makes the rest of this reliable. Content-Disposition: attachment names the saved file and removes any doubt about rendering.
Server configuration
extension mappingnginx
types {
audio/midi mid midi;
}Apache
AddType audio/midi .mid .midiCaddy
@type path *.mid *.midi
header @type Content-Type "audio/midi"Extensions and other spellings
with signatureFile extensions
Also written as
These reach the same handler in practice. Accept them on input; send audio/midi on output.
File signature
4D 54 68 64
Check these bytes rather than the client-supplied Content-Type when validating an upload. The header is a claim; the signature is evidence.