Bug 56499 – webkit-patch does not support HTTPS proxies due to old version of Mechanize

• Component: Tools / Tests
• Status: RESOLVED FIXED

[Keith Kyzivat]

webkit-patch currently does not support HTTPS proxies.  Many companies use proxies to access the public internet, and this is needed in order to be able to use webkit-patch.

This is due to a limitation in the older version of mechanize that we use.
Mechanize supports HTTPS proxies in newer versions of Mechanize, and I have determined that version 0.2.4 works fine with webkit-patch upload (I have not tested more than that).

Here is a post from the author of mechanize indicating that HTTPS proxy support was present in his git repo as of 31-Jan-2010, and it's been a year since then, and 5 releases since 0.1.11.
http://blog.gmane.org/gmane.comp.python.wwwsearch.general/month=20100201
http://pypi.python.org/packages/source/m/mechanize/

I would like to see the webkit scripts update to use mechanize 0.2.4 if possible.

[Keith Kyzivat]

Created attachment 85996 [details]
Patch

update mechanize to 0.2.4

[Andreas Kling]

CC'ing folks who have poked the autoinstall stuff in the past.

[Adam Barth]

Comment on attachment 85996 [details]
Patch

Looks fine, but Eric should take a look too.

[Eric Seidel (no email)]

Comment on attachment 85996 [details]
Patch

LGTM!  Thanks!

[WebKit Commit Bot]

Comment on attachment 85996 [details]
Patch

Clearing flags on attachment: 85996

Committed r81348: <http://trac.webkit.org/changeset/81348>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.