Message235590
The relevant code looks like it is _parse_proxy() at Lib/urllib/request.py:693. It has custom code to search for a slash (/), so it wouldn’t be hard to make it search after the last at (@) symbol. (I previously assumed it would use urlsplit() or similar, which would be harder to adjust.)
Even Curl seems to require an @ symbol in the username or password to be encoded, i.e. the following doesn’t work, so you still need to encode the fields in general to work with Curl.
http_proxy=http://a@x:b@localhost curl . . .
http_proxy=http://a:b@x@localhost curl . . . |
|
Date |
User |
Action |
Args |
2015-02-09 05:44:16 | martin.panter | set | recipients:
+ martin.panter, orsenthil, Andy.Reitz |
2015-02-09 05:44:16 | martin.panter | set | messageid: <1423460656.01.0.909280228351.issue23328@psf.upfronthosting.co.za> |
2015-02-09 05:44:16 | martin.panter | link | issue23328 messages |
2015-02-09 05:44:15 | martin.panter | create | |
|