Returning Values from Forms: multipart/form-data
RFC 7578

Document Type RFC - Proposed Standard (July 2015; Errata)
Obsoletes RFC 2388
Last updated 2016-04-27
Replaces draft-masinter-multipart-form-data
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication Dec 2014
Document shepherd Salvatore Loreto
Shepherd write-up Show (last changed 2014-12-15)
IESG IESG state RFC 7578 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Barry Leiba
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                       L. Masinter
Request for Comments: 7578                                         Adobe
Obsoletes: 2388                                                July 2015
Category: Standards Track
ISSN: 2070-1721

            Returning Values from Forms: multipart/form-data

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7578.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Masinter                     Standards Track                    [Page 1]
RFC 7578                   multipart/form-data                 July 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Percent-Encoding Option . . . . . . . . . . . . . . . . . . .   3
   3.  Advice for Forms and Form Processing  . . . . . . . . . . . .   3
   4.  Definition of multipart/form-data . . . . . . . . . . . . . .   4
     4.1.  "Boundary" Parameter of multipart/form-data . . . . . . .   4
     4.2.  Content-Disposition Header Field for Each Part  . . . . .   4
     4.3.  Multiple Files for One Form Field . . . . . . . . . . . .   5
     4.4.  Content-Type Header Field for Each Part . . . . . . . . .   5
     4.5.  The Charset Parameter for "text/plain" Form Data  . . . .   5
     4.6.  The _charset_ Field for Default Charset . . . . . . . . .   6
     4.7.  Content-Transfer-Encoding Deprecated  . . . . . . . . . .   6
     4.8.  Other "Content-" Header Fields  . . . . . . . . . . . . .   7
   5.  Operability Considerations  . . . . . . . . . . . . . . . . .   7
     5.1.  Non-ASCII Field Names and Values  . . . . . . . . . . . .   7
       5.1.1.  Avoid Non-ASCII Field Names . . . . . . . . . . . . .   7
       5.1.2.  Interpreting Forms and Creating multipart/form-data
               Data  . . . . . . . . . . . . . . . . . . . . . . . .   7
       5.1.3.  Parsing and Interpreting Form Data  . . . . . . . . .   8
     5.2.  Ordered Fields and Duplicated Field Names . . . . . . . .   8
     5.3.  Interoperability with Web Applications  . . . . . . . . .   8
     5.4.  Correlating Form Data with the Original Form  . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Media Type Registration for multipart/form-data . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Changes from RFC 2388  . . . . . . . . . . . . . . .  14
   Appendix B.  Alternatives . . . . . . . . . . . . . . . . . . . .  14
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  15
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   In many applications, it is possible for a user to be presented with
   a form.  The user will fill out the form, including information that
   is typed, generated by user input, or included from files that the
   user has selected.  When the form is filled out, the data from the
   form is sent from the user to the receiving application.

   The definition of multipart/form-data is derived from one of those
   applications, originally set out in [RFC1867] and subsequently
Show full document text