13788 2011-08-15 15:45:37 +0000 I think Gecko at least uses a charset parameter here that should probably be documented if more widely adopted. 2011-10-04 23:51:49 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#application/x-www-form-urlencoded P3 normal --- 1 contributor ian annevk bzbarsky ian jonas mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 55096 0 contributor 2011-08-15 15:45:37 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/iana.html Multipage: http://www.whatwg.org/C#application/x-www-form-urlencoded Complete: http://www.whatwg.org/c#application/x-www-form-urlencoded Comment: I think Gecko at least uses a charset parameter here that should probably be documented if more widely adopted. Posted from: 83.85.115.123 by annevk@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.0; U; en) Presto/2.9.168 Version/11.50 55637 1 ian 2011-08-23 00:06:05 +0000 Can you elaborate? Do you have any test cases demonstrating what you mean? 55670 2 annevk 2011-08-23 08:10:59 +0000 I believe Gecko at some point changed to include the charset parameter in form submissions (in the Content-Type) indicating the encoding of the data submitted. 55673 3 bzbarsky 2011-08-23 08:29:55 +0000 That was for the parts of a multipart submission. For urlencoded submissions, we have some code to put the charset parameter in, but it's been ifdefed out for nearly 12 years now. There is relevant discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=7533 (note all the duplicates) and https://bugzilla.mozilla.org/show_bug.cgi?id=18431#c2 (which is a list of things that were broken at the time with the charset in the header). So at least as of 1999 sending a charset here was not compatible with the web. I doubt much has changed since, sadly. At least we have _charset_.... 57824 4 ian 2011-10-04 23:51:49 +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: see comment 3 for the specific proposal here. As far as multipart submission goes, the spec currently says that no Content-Type is included at all, so it's not clear exactly what is needed, if anything. Please file a separate bug for that one if you want something changed there.