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 jaraco
Recipients ammar2, benjamin.peterson, gregory.p.smith, jaraco, larry, lukasz.langa, mcepl, ned.deily, tburke, webknjaz, xtreak
Date 2019-09-20.14:03:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for all the comments. I agree the current (secure by default) implementation is desirable.  I also agree that such usage was never explicitly supported, so the "regression" here is perhaps over-stated. What I seek is to avoid the Go recommendation of "fork the implementation" when a lightweight hook could be provided as a means to achieve a reasonable, if unusual and discouraged, behavior. In particular, I'd like to support:

Sending a single request with invalid bytes for the path.
Allowing all requests for a client to support invalid bytes on the path.

Ideally, the solution should allow sending other non-control bytes as well, supporting the use case reported in issue36274 also.

I'll draft a patch. I'll try to get to it this weekend, but if I don't, don't feel like this needs to block releases.
Date User Action Args
2019-09-20 14:03:13jaracosetrecipients: + jaraco, gregory.p.smith, larry, benjamin.peterson, ned.deily, mcepl, lukasz.langa, webknjaz, ammar2, tburke, xtreak
2019-09-20 14:03:13jaracosetmessageid: <>
2019-09-20 14:03:13jaracolinkissue38216 messages
2019-09-20 14:03:13jaracocreate