How to run Mercurial on Suse SLES 11 SP1 behind proxy with authentication ?

[Giovanni Gherdovich]

:::: 2014/1/17 Matt Mackall <mpm at selenic.com>
::::
::::     On Fri, 2014-01-17 at 20:19 +0100, Luca Toldo wrote:
::::     > Dear experts,
::::     > I have a server running Suse SLES 11 SP1 behind proxy with
authentication.
::::     > hg clone https://....
::::     > does not work since urllib2 (that is used by mercurial) does not
::::     > appropriately handle proxy with authentication.
::::     > Can you please instruct me what to do ?
::::     > I thought to install urllib3 and then recompile mercurial using
urllib3
::::     > instead of urllib2 however I couldn't find anyone describing it
in the net
::::     > and therefore I do not feel sure.
::::     > Could you please instruct me ?
::::     You may be able to set your proxy username and password in your
proxy
::::     URLs. For instance:
::::
::::     $ set http_proxy = http://myname:mypass@proxy.derpcorp.com/
::::
::::     You're going to have a bad time trying to replace libraries.


or you can use tinyproxy:
https://banu.com/tinyproxy/

tinyproxy is on your local machine, it talks to the external proxy and
handles the auth, you talk to tinyproxy with no auth.

proxy  <---auth--->  tinyproxy on localhost  <---->  hg

it served me well when many things needed to access
the external proxy, not only hg: curl, wget, package manager...
tinyproxy centralized everything and if I changed credentials
I had to do it in only one place.

GGhh

PS: I don't know if tinyproxy is packaged for Suse.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140117/3d34d8f4/attachment-0002.html>