View Source MIME (mime v2.0.3)
Maps MIME types to its file extensions and vice versa.
MIME types can be extended in your application configuration as follows:
config :mime, :types, %{
"application/vnd.api+json" => ["json-api"]
}After adding the configuration, MIME needs to be recompiled. If you are using mix, it can be done with:
$ mix deps.clean mime --build
Link to this section Summary
Functions
Returns the custom types compiled into the MIME module.
Returns the extensions associated with a given MIME type.
Guesses the MIME type based on the path's extension. See type/1.
Returns whether an extension has a MIME type registered.
Returns the MIME type associated with a file extension.
Link to this section Functions
Returns the custom types compiled into the MIME module.
Returns the extensions associated with a given MIME type.
examples
Examples
iex> MIME.extensions("text/html")
["html", "htm"]
iex> MIME.extensions("application/json")
["json"]
iex> MIME.extensions("application/vnd.custom+xml")
["xml"]
iex> MIME.extensions("foo/bar")
[]Guesses the MIME type based on the path's extension. See type/1.
examples
Examples
iex> MIME.from_path("index.html")
"text/html"Returns whether an extension has a MIME type registered.
examples
Examples
iex> MIME.has_type?("txt")
true
iex> MIME.has_type?("foobarbaz")
falseReturns the MIME type associated with a file extension.
If no MIME type is known for file_extension,
"application/octet-stream" is returned.
examples
Examples
iex> MIME.type("txt")
"text/plain"
iex> MIME.type("foobarbaz")
"application/octet-stream"