[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Changes by Serhiy Storchaka : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Roundup Robot added the comment: New changeset 04e95f05aafe by Serhiy Storchaka in branch '2.7': Issue #9006: Added tests for XML RPC with non-UTF-8 encoding. https://hg.python.org/cpython/rev/04e95f05aafe New changeset 59cb8811286a by Serhiy Storchaka in branch '3.5': Issue #9006: Added tests f

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Changes by Serhiy Storchaka : Added file: http://bugs.python.org/file41634/test_xmlrpc_encoding-3.5.patch ___ Python tracker ___ ___ Python-bug

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Serhiy Storchaka added the comment: xmlrpc uses XML. This format includes information about the encoding and doesn't need external specification. The server in the example is not correct. It generates XML with default XML declaration that implies the UTF-8 encoding, but the body is encoded wit

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Éric Araujo added the comment: Could you reupload your fix as a diff instead of a whole file? See http://www.python.org/dev/patches/ for some help. -- nosy: +loewis type: crash -> behavior versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 _

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Timothée CEZARD added the comment: With 2.7 I'm getting another exception xml.parsers.expat.ExpatError: not well-formed (invalid token): line 5, column 15 where with 2.6 I was getting UnicodeDecodeError: 'utf8' codec can't decode byte 0xa3 in position 0: unexpected code byte I didn't try with

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

Éric Araujo added the comment: Thank your for reporting this bug. Are you able to reproduce the bug with current development versions, a.k.a. 2.7 (svn trunk, or the rc release) and 3.2 (py3k branch)? Only security and documentation fixes go in stable releases like 2.6 and 3.1. Also, please up

[issue9006] xml-rpc Server object does not propagate the encoding to Unmarshaller

New submission from Timothée CEZARD : xmlrpc cleint (Server class) default encoding is utf-8 it can be modified through the encoding keyword parameter. This parameter is not passed to the Unmarshaller that decode the bit flow causing the server to crash attached is two script reproducing the i