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 gregory.p.smith
Recipients gregory.p.smith, martin.panter, orange, serhiy.storchaka, vstinner, ware, xiang.zhang, xtreak
Date 2019-04-10.19:31:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> *Maybe* we need to provide a way to allow to pass junk characters in an URL? (disable URL validation)

We should not do this in our http protocol stack code.  Anyone who _wants_ that is already intentionally violating the http protocol which defeats the entire purpose of our library and the parameter named "url".

Will this break something in the world other than our own test_xmlrpc test?  Probably.  Do they have a right to complain about it?  Not one we need listen to.  Such code is doing something that was clearly an abuse of the API.  The parameter was named url not raw_data_to_stuff_subversively_into_the_binary_protocol.  Its intent was clear.
Date User Action Args
2019-04-10 19:31:06gregory.p.smithsetrecipients: + gregory.p.smith, vstinner, martin.panter, serhiy.storchaka, xiang.zhang, orange, xtreak, ware
2019-04-10 19:31:06gregory.p.smithsetmessageid: <>
2019-04-10 19:31:06gregory.p.smithlinkissue30458 messages
2019-04-10 19:31:05gregory.p.smithcreate