Header field: Content-Type
MIME content type
- Applicable protocol:
- MIME (http://www.rfc-editor.org/rfc/rfc2045.txt)
- Status:
- standards-track
- Author/Change controller:
-
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force.
- Specification document(s):
- http://www.rfc-editor.org/rfc/rfc2045.txt (section 5)
- Related information:
- Format of content (character set etc.) Note that the values
for this header field are defined in different ways in
RFC 1049 and in MIME (RFC 2045), look for the 'MIME-version'
header field to understand if Content-Type is to be
interpreted according to RFC 1049 or according to MIME.
The MIME definition should be used in generating mail.
RFC 1049 has 'historic' status. RFC 1766 defines a parameter
'difference' to this header field.
Various other Content-Type define various additional parameters.
For example, the parameter 'charset' is mandatory for all
textual Content-Types.
See also: RFC 1049, RFC 1123: 5.2.13, RFC 1766: 4.1.