- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Sep 2010 13:24:43 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10567 Animal <nigelw@forwardcomputers.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nigelw@forwardcomputers.co. | |uk --- Comment #1 from Animal <nigelw@forwardcomputers.co.uk> 2010-09-07 13:24:42 --- 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? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 7 September 2010 13:24:44 UTC