RFC 7578: Returning Values from Forms: multipart/form-data
In plain English — editorial summary, not part of the RFC
This specification defines the multipart/form-data media type, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. This document obsoletes RFC 2388.
Document record
- Document ID
- RFC7578
- Published
- July 2015
- Authors
- L. Masinter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 15
- Also known as
- —
- Obsoletes:
- RFC 2388
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2298An Extensible Message Format for Message Disposition NotificationsObsoleted
March 1998
- RFC 2586The Audio/L16 MIME content typeCurrent
May 1999
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 3950Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationCurrent
February 2005
- RFC 3949File Format for Internet FaxCurrent
February 2005
- RFC 3250Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationObsoleted
September 2002
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?