Skip to content
Permalink
Browse files
[e] (0) add a note to clarify interaction with rfc 2388
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12065

git-svn-id: http://svn.whatwg.org/webapps@6051 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed May 3, 2011
1 parent f381d25 commit b327308c563c42b6ede0041873fe568179a4bacf
Showing with 19 additions and 0 deletions.
  1. +6 −0 complete.html
  2. +6 −0 index
  3. +7 −0 source
@@ -51296,6 +51296,12 @@ <h5 id=multipart-form-data><span class=secno>4.10.22.6 </span>Multipart form dat
the <var title="">form data set</var>. Multiple entries with the
same name must be treated as distinct fields.</p>

<p class=note>In particular, this means that multiple files
submitted as part of a single <code title="">&lt;input&nbsp;type=file&nbsp;multiple&gt;</code> element
will result in each file having its own field; the "sets of files"
feature ("<code title="">multipart/mixed</code>") of RFC 2388 is
not used.</p>

<p>The parts of the generated <code title="">multipart/form-data</code> resource that correspond to
non-file fields must not have a <code><a href=#content-type>Content-Type</a></code> header
specified. Their names and values must be encoded using the
6 index
@@ -51324,6 +51324,12 @@ fur
the <var title="">form data set</var>. Multiple entries with the
same name must be treated as distinct fields.</p>

<p class=note>In particular, this means that multiple files
submitted as part of a single <code title="">&lt;input&nbsp;type=file&nbsp;multiple&gt;</code> element
will result in each file having its own field; the "sets of files"
feature ("<code title="">multipart/mixed</code>") of RFC 2388 is
not used.</p>

<p>The parts of the generated <code title="">multipart/form-data</code> resource that correspond to
non-file fields must not have a <code><a href=#content-type>Content-Type</a></code> header
specified. Their names and values must be encoded using the
7 source
@@ -57877,6 +57877,13 @@ fur
the <var title="">form data set</var>. Multiple entries with the
same name must be treated as distinct fields.</p>

<p class="note">In particular, this means that multiple files
submitted as part of a single <code
title="">&lt;input&nbsp;type=file&nbsp;multiple></code> element
will result in each file having its own field; the "sets of files"
feature ("<code title="">multipart/mixed</code>") of RFC 2388 is
not used.</p>

<p>The parts of the generated <code
title="">multipart/form-data</code> resource that correspond to
non-file fields must not have a <code>Content-Type</code> header

0 comments on commit b327308

Please sign in to comment.