- From: <bugzilla@jessica.w3.org>
- Date: Sat, 10 Mar 2012 04:41:17 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16302 Summary: possible unnecessary insertion of U+0020 SPACE in mime type expression Product: WebAppsWG Version: unspecified Platform: All URL: http://dvcs.w3.org/hg/xhr/raw-file/8d4e9ccfdbd4/Overvi ew.html#the-send()-method OS/Version: All Status: NEW Severity: normal Priority: P2 Component: XHR AssignedTo: annevk@opera.com ReportedBy: glenn@skynav.com QAContact: public-webapps-bugzilla@w3.org CC: mike@w3.org, public-webapps@w3.org In section 4.7.6, step 3, under "If data is a FormData", the text specifies: "Let mime type be the concatenation of "multipart/form-data;", a U+0020 SPACE character, "boundary=", and ..." The text ", a U+0020 SPACE character" is unnecessary and undesirable, unless it is here for some unstated compatibility reason. HTML5 references HTTP (RFC2616) for the definition of a MIME type, which defines it as follows: media-type = type "/" subtype *( ";" parameter ) parameter = attribute "=" value attribute = token value = token | quoted-string and which does not show the insertion of SPACE after ";" However, I would note that the examples of multipart/form-data in RFC2046 (HTTP 1.0) 5.1.1 [1] and HTML4 [2] do show SPACE after ";". So there may be a hidden compatibility argument operating here. If that is the case, then please add a note explaining it with an informative reference to another document justifying/defining this usage. [1] http://tools.ietf.org/html/rfc2616#section-3.7 [2] http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.2 -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Saturday, 10 March 2012 04:41:19 UTC