Returning Values from Forms: multipart/form-data
draft-masinter-multipart-form-data-00

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Last updated 2013-09-16 (latest revision 2013-09-15)
Replaced by RFC 7578, RFC 7578
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        L. Masinter
Internet-Draft                                                     Adobe
Obsoletes: 2388 (if approved)                         September 15, 2013
Intended status: Standards Track
Expires: March 17, 2014

            Returning Values from Forms: multipart/form-data
                 draft-masinter-multipart-form-data-00

Abstract

   This specification defines an Internet Media Type, multipart/form-
   data, 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.  It
   replaces RFC 2388.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 17, 2014.

Copyright Notice

   Copyright (c) 2013 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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Definition of multipart/form-data  . . . . . . . . . . . . . .  2

Masinter                 Expires March 17, 2014                 [Page 1]
Internet-Draft            multipart/form-data             September 2013

   3.  Use of multipart/form-data . . . . . . . . . . . . . . . . . .  3
     3.1.  Boundary . . . . . . . . . . . . . . . . . . . . . . . . .  3
     3.2.  Sets of files  . . . . . . . . . . . . . . . . . . . . . .  3
     3.3.  Encoding . . . . . . . . . . . . . . . . . . . . . . . . .  3
     3.4.  Other attributes . . . . . . . . . . . . . . . . . . . . .  3
     3.5.  Charset of text in form data . . . . . . . . . . . . . . .  4
   4.  Operability considerations . . . . . . . . . . . . . . . . . .  4
     4.1.  Compression, encryption  . . . . . . . . . . . . . . . . .  4
     4.2.  Non-ASCII field names and values . . . . . . . . . . . . .  4
     4.3.  Ordered fields and duplicated field names  . . . . . . . .  5
     4.4.  Interoperability with web applications . . . . . . . . . .  5
     4.5.  Correlating form data with the original form . . . . . . .  5
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   6.  Media type registration for multipart/form-data  . . . . . . .  6
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  6
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  7
   Appendix A. Changes from RFC . . . . . . . . . . . . . . . . . . .  7
   Appendix B. Alternatives . . . . . . . . . . . . . . . . . . . . .  8
     Appendix B.1.  Other data encodings rather than multipart  . . .  8
     Appendix B.2.  Remote files with third-party transfer  . . . . .  8
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  8

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
   incorporated into [HTML3.2] and [HTML4.0], where forms are expressed
   in HTML, and in which the form values are sent via HTTP or electronic
   mail.  This representation is widely implemented in numerous web
   browsers and web servers.

   However, multipart/form-data can be used for forms that are presented
   using representations other than HTML (spreadsheets, Portable
Show full document text