This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients docs@python, martin.panter, orsenthil, r.david.murray
Date 2015-11-08.10:56:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1446980196.52.0.665789638883.issue25576@psf.upfronthosting.co.za>
In-reply-to
Content
I think the server bugs referenced by the Mozilla bug are mainly about servers that do not recognize the content type at all, due the the presence of any charset parameter. They probably do something like “if headers['Content-Type'] == 'application/x-www-form-urlencoded' ” without checking for parameters first. So it wouldn’t matter if it was charset=latin-1 or charset=utf-8.

A couple comments in the Mozilla bug say that including “charset” is specified by a HTTP standard, but I suspect this may be a mistake. Perhaps this is the best evidence for my argument, from <http://www.w3.org/TR/html/forms.html#url-encoded-form-data>:

'''
Parameters on the “application/x-www-form-urlencoded” MIME type are ignored. In particular, this MIME type does not support the “charset” parameter.
'''
History
Date User Action Args
2015-11-08 10:56:36martin.pantersetrecipients: + martin.panter, orsenthil, r.david.murray, docs@python
2015-11-08 10:56:36martin.pantersetmessageid: <1446980196.52.0.665789638883.issue25576@psf.upfronthosting.co.za>
2015-11-08 10:56:36martin.panterlinkissue25576 messages
2015-11-08 10:56:36martin.pantercreate