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 xrg
Recipients xrg
Date 2011-04-08.09:33:01
SpamBayes Score 0.000419997
Marked as misclassified No
Message-id <1302255183.42.0.728288108717.issue11804@psf.upfronthosting.co.za>
In-reply-to
Content
The expat library (in C level) is not xml 1.1 compliant, meaning that
it won't accept characters \x01-\x08,\x0b,\x0c and \x0e-\x1f .
At the same time, ElementTree (or custom XML creation, such as in xmlrpclib.py:694) allow these characters to pass through. They will get blocked on the receiving side.
Since 2.7, the expat library is the default parser for xml-rpc, so it
this is a regression, IMHO. According to the network principal, we should
accept these characters gracefully.

The attached test script demonstrates that we're not xml 1.1 compliant (but instead enforce the more strict 1.0 rule)

References:
http://bugs.python.org/issue5166
http://en.wikipedia.org/wiki/Valid_characters_in_XML
History
Date User Action Args
2011-04-08 09:33:03xrgsetrecipients: + xrg
2011-04-08 09:33:03xrgsetmessageid: <1302255183.42.0.728288108717.issue11804@psf.upfronthosting.co.za>
2011-04-08 09:33:02xrglinkissue11804 messages
2011-04-08 09:33:02xrgcreate