12065 – Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP.

This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12065 - Please point out that for <input type=file multiple> http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead each file should have its own field. Otherwise you break PHP.

Summary: Please point out that for <input type=file multiple> http://tools.ietf.org/ht...

Status:	RESOLVED FIXED

Alias:	None

Product:	HTML WG
Classification:	Unclassified
Component:	LC1 HTML5 spec (show other bugs)
Version:	unspecified
Hardware:	Other other

Importance:	P3 normal
Target Milestone:	---
Assignee:	Ian 'Hixie' Hickson
QA Contact:	HTML WG Bugzilla archive list

URL:	http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-02-14 15:47 UTC by contributor
Modified:	2011-08-04 05:17 UTC (History)
CC List:	7 users (show)

See Also:

Attachments

Description contributor 2011-02-14 15:47:18 UTC

Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#multipart-form-data

Comment:
Please point out that for <input type=file multiple>
http://tools.ietf.org/html/rfc2388#section-4.2 should not be used. Instead
each file should have its own field. Otherwise you break PHP. 

Posted from: 83.85.115.123 by annevk@opera.com

Comment 1 Anne 2011-02-14 15:49:48 UTC

(I still think we should just take over the definition of multipart/form-data by the way. It would make things much clearer.)

Comment 2 Ian 'Hixie' Hickson 2011-02-14 19:13:08 UTC

There's actually no conflict with the RFC here, and the spec is technically already correct, though I will be sure to add a note explaining this case.

The RFC says that you can use multipart/mixed only if a single form field has multiple files as a set, but in the case of an <input type=file multiple> control, each file generates a separate form field in the form data set.

As an aside: it wouldn't take much to get me to rewrite that RFC into the HTML spec and give up on using it as an external reference, because it's not the most well-written of RFCs. But if it's not truly needed, which so far it seems it has not been, then I'd rather spend the time working on more important things.

Comment 3 Anne 2011-02-15 00:21:44 UTC

Adding a note sounds good.

Comment 4 Ian 'Hixie' Hickson 2011-05-03 19:22:07 UTC

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.

Comment 5 contributor 2011-05-03 19:23:13 UTC

Checked in as WHATWG revision r6051.
Check-in comment: add a note to clarify interaction with rfc 2388
http://html5.org/tools/web-apps-tracker?from=6050&to=6051

Comment 6 Michael[tm] Smith 2011-08-04 05:17:01 UTC

mass-move component to LC1