Backporting HTTPS via Proxy Support in urllib2
Issue: http://bugs.python.org/issue1424152 mentions about HTTPS Support via proxy in urllib2. This is fixed in the trunk (Revision 72880), but there has been number of valid requests to backport it Python 2.6. While I agree and ready to backport to Python 2.6, I would like to ask here if there are any objections in this front. I am ready with the Python 3.x patch as well (with tests passed and tested under proxy setup). I shall apply that too, which is pending for a while now. :( -- Senthil Wad some power the giftie gie us To see oursels as others see us. -- R. Burns
This is fixed in the trunk (Revision 72880), but there has been number of valid requests to backport it Python 2.6. While I agree and ready to backport to Python 2.6, I would like to ask here if there are any objections in this front.
In msg76855 Greg ruled that it is a new feature, and thus cannot be backported. I trust his judgement - so to convince me, you would need to convince Greg first :-) Regards, Martin
On Sat, Jul 25, 2009 at 2:53 AM, "Martin v. Löwis"<martin@v.loewis.de> wrote:
This is fixed in the trunk (Revision 72880), but there has been number of valid requests to backport it Python 2.6. While I agree and ready to backport to Python 2.6, I would like to ask here if there are any objections in this front.
In msg76855 Greg ruled that it is a new feature, and thus cannot be backported. I trust his judgement - so to convince me, you would need to convince Greg first :-)
Regards, Martin
So long as the new set_tunnel() method is hidden in the backport I'm fine with the patch. It fixes urllib2 do the right thing with https and a proxy without any public API change. -Greg
participants (3)
-
"Martin v. Löwis" -
Gregory P. Smith -
Senthil Kumaran