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 13788 - I think Gecko at least uses a charset parameter here that should probably be documented if more widely adopted.
Summary: I think Gecko at least uses a charset parameter here that should probably be ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: 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-08-15 15:45 UTC by contributor
Modified: 2011-10-04 23:51 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2011-08-15 15:45:37 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2011-08-23 00:06:05 UTC 
Can you elaborate? Do you have any test cases demonstrating what you mean?
Comment 2 Anne 2011-08-23 08:10:59 UTC 
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.
Comment 3 Boris Zbarsky 2011-08-23 08:29:55 UTC 
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_....
Comment 4 Ian 'Hixie' Hickson 2011-10-04 23:51:49 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: 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.