Content type and charset
02Type/subtype and parameters identify how recovered content should be interpreted.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5.1 ↗
RFC 2045 · § 5.1EXAMPLE
3 / 3
03
Keep defaults explicit
Absent metadata has a specified historical default rather than arbitrary guessing.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
A charset parameter describes text character encoding.
- A charset parameter describes text character encoding.
- Missing Content-Type normally defaults to text/plain with charset US-ASCII under this specification.
- Unknown parameters and types have defined handling; do not execute arbitrary content merely because it is labeled.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy