Returning Values from Forms: multipart/form-data
draft-ietf-appsawg-multipart-form-data-01

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Last updated 2014-02-14
Replaces draft-masinter-multipart-form-data
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document (wg milestone: Dec 2014 - Publication requeste... )
Document shepherd Salvatore Loreto
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)                          February 14, 2014
Intended status: Standards Track
Expires: August 16, 2014

            Returning Values from Forms: multipart/form-data
               draft-ietf-appsawg-multipart-form-data-01

Abstract

   This specification (re)defines the multipart/form-data Internet 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.  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 August 16, 2014.

Copyright Notice

   Copyright (c) 2014 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.  NOTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2

Masinter                Expires August 16, 2014                 [Page 1]
Internet-Draft            multipart/form-data              February 2014

   3.  Form requirements  . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Definition of multipart/form-data  . . . . . . . . . . . . . .  3
     4.1.  Boundary . . . . . . . . . . . . . . . . . . . . . . . . .  3
     4.2.  filename attribute . . . . . . . . . . . . . . . . . . . .  3
     4.3.  Multiple files for one form field  . . . . . . . . . . . .  4
     4.4.  Content-Type . . . . . . . . . . . . . . . . . . . . . . .  4
     4.5.  The charset parameter  . . . . . . . . . . . . . . . . . .  4
     4.6.  The _charset_ field  . . . . . . . . . . . . . . . . . . .  4
     4.7.  Content-Transfer-Encoding  . . . . . . . . . . . . . . . .  5
     4.8.  Other Content- headers . . . . . . . . . . . . . . . . . .  5
   5.  Operability considerations . . . . . . . . . . . . . . . . . .  5
     5.1.  Non-ASCII field names and values . . . . . . . . . . . . .  5
       5.1.1.  Avoid creating forms with non-ASCII field names  . . .  5
       5.1.2.  Ampersand hash encoding  . . . . . . . . . . . . . . .  5
       5.1.3.  Interpreting forms and creating form-data  . . . . . .  6
       5.1.4.  Parsing and interpreting form data . . . . . . . . . .  6
     5.2.  Ordered fields and duplicated field names  . . . . . . . .  6
     5.3.  Interoperability with web applications . . . . . . . . . .  7
     5.4.  Correlating form data with the original form . . . . . . .  7
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   7.  Media type registration for multipart/form-data  . . . . . . .  8
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     8.1.  Normative References . . . . . . . . . . . . . . . . . . .  8
     8.2.  Informative References . . . . . . . . . . . . . . . . . .  9
   Appendix A. Changes from RFC 2388  . . . . . . . . . . . . . . . .  9
   Appendix B. Alternatives . . . . . . . . . . . . . . . . . . . . .  9
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.  NOTE

   There is a GitHub repository for this draft at https://github.com/
   masinter/multipart-form-data along with an issue tracker.  This
   specification has been proposed as a work item of the APPSAWG
   Applications Area working group, apps-discuss@ietf.org.  Please raise
   issues in the tracker, or send to the apps-discuss list.

2.  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
Show full document text