[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

Roundup Robot added the comment: New changeset 16fec577fd8b by Martin Panter in branch '3.4': Issue #25576: Remove application/x-www-form-urlencoded charset advice https://hg.python.org/cpython/rev/16fec577fd8b New changeset 95ae5262d27c by Martin Panter in branch '3.5': Issue #25576: Merge

[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

Changes by Martin Panter : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

R. David Murray added the comment: OK, I'll accept that as authoritative :) One very minor comment in the review, otherwise looks good to me. -- ___ Python tracker

[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

Martin Panter added the comment: The second version of the patch changes some more examples in the how-to to data.encode("ascii"). I’ll leave this open for a bit in case Senthil is around and wants to comment (seeing as he added the text I am removing). -- Added file:

[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

Martin Panter added the comment: 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'] ==

[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

New submission from Martin Panter: I understand using a “charset” parameter with “Content-Type: application/x-www-form-urlencoded” is not standardized. Since Issue 11082, the documentation advises to use it, but I propose to remove this advice. HTML 5 mentions setting a _charset_ parameter,

[issue25576] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice

R. David Murray added the comment: Although I didn't read through the whole thing, the mozilla bug discussion indicates this is the correct way to specify the charset, it's just that there was lots of buggy software that didn't handle setting it to latin-1. Is the same true for setting it to