Visual RFC.
ALL RFCs / RFC 4180
Read the RFC ↗
RFC 4180 / MECHANISM GUIDE

Media type and application limits

05

text/csv describes a textual interchange format, not a complete typed schema.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3 ↗
RFC 4180 · § 3EXAMPLE
3 / 3
Media type and application limitstext/csv describes a textual interchange format, not a complete typed schema.Media type and application limitsContent-Type: text/csv; header=presentname → stringscore → numberTyping and safe import are application decisions
03
Keep text from becoming code

A spreadsheet or other consumer needs its own safe import policy.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Optional charset and header parameters are defined.

  • Optional charset and header parameters are defined.
  • CSV does not define numeric, date, formula, or identifier interpretation.
  • Consumers must agree on schema and safe treatment of values; delimiter and line-ending variants need explicit handling.
DETAILS

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
All chapters in this RFC
  1. Records and fields
  2. Optional header row
  3. Quoted fields
  4. Escape double quotes
  5. Media type and application limits

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗