10567 2010-09-07 13:09:33 +0000 How will the input name be processed for multiple files? can mime/multipart "part" names be the same? 2010-10-04 15:04:56 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#the-input-element-as-a-file-upload-control P3 normal --- 1 contributor ian ian mike nigelw public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 38510 0 contributor 2010-09-07 13:09:33 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-input-element-as-a-file-upload-control Comment: How will the input name be processed for multiple files? can mime/multipart "part" names be the same? Posted from: 80.177.128.34 38512 1 nigelw 2010-09-07 13:24:42 +0000 In the document http://www.ietf.org/rfc/rfc2388.txt We have 3. Definition of multipart/form-data The media-type multipart/form-data follows the rules of all multipart MIME data streams as outlined in [RFC 2046]. In forms, there are a series of fields to be supplied by the user who fills out the form. Each field has a name. Within a given form, the names are unique. "multipart/form-data" contains a series of parts. Each part is expected to contain a content-disposition header [RFC 2183] where the disposition type is "form-data", and where the disposition contains an (additional) parameter of "name", where the value of that parameter is the original field name in the form. For example, a part might contain a header: Content-Disposition: form-data; name="user" with the value corresponding to the entry of the "user" field. So how can <input type="file" name="myPhotos" multiple="true"> be submitted? 39441 2 ian 2010-09-26 02:40:47 +0000 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: Rejected Change Description: no spec change Rationale: RFC2388 is wrong, field names aren't necessarily unique. <input type=file name=a multiple> with two files selected gets submitted exactly as would: <input type=file name=a> <input type=file name=a> ...each with one file selected. 40555 3 nigelw 2010-10-04 15:04:56 +0000 So there may be multuiple parts with Content-Disposition: form-data; name="user" As the header? Right, I'll have to rethink my MuliPartMessage class. It use the Java Mail API to parse a multipart message, but then stashes the Parts in a HashMap keyed by the *name* part of the Content-Disposition