Mercruial ignoring http_proxy settings

Augie Fackler raf at durin42.com
Thu Jan 5 09:16:29 CST 2012


On Jan 3, 2012, at 6:58 AM, Ton Plomp wrote:
> 
> The thing is weird.
> 
> other repositories (bitbucket for instance) are being routed through the
> proxy.
> If I use a slightly changed URL I get an:
> 
> abort:error:getaddrinfo failed
> 
> I've traced all mercurial.ini and nowhere can I find a special issue for
> this address.

can you try this again with
[ui]
usehttp2=true

and see if the problem goes away? If it doesn't, can you add
[ui]
http2debuglevel=info

and send me the (possibly-redacted, if need be) verbose output from the http backend?

> 
> Ton
> 
> 
> 
> 
> 2011/12/14 Ton Plomp <tcplomp at gmail.com>
> 
>> I've run the command with --debug, and I see that that mercurial says it's
>> proxying...
>> I can't run any more tests today, but tomorrow I'll see if I can norrow
>> this a little bit more, any insight is welcomed.
>> 
>> Ton
>> 
>> 2011/12/14 Martin Geisler <mg at aragost.com>
>> 
>>> Ton Plomp <tcplomp at gmail.com> writes:
>>> 
>>>> Hi,
>>>> 
>>>> I'm trying to connect to a mercurial repo via a proxy, setting the
>>>> proxy with TortoiseHG didin't work, so I tried to actively set the
>>>> http_proxy.host via the CMD with the following command:
>>>> 
>>>> hg --config http_proxy.host=10.192.132.191:5865 --config
>>>> http_proxy.always=true incoming thuis
>>>> 
>>>> MS-network logs shows that hg directly tries to connect to 'thuis'
>>>> instead of going through the proxy.
>>>> 
>>>> I'm using the same proxy on another computer without any issues.
>>>> 
>>>> The computer is running WinXP and connected to a windows domain (the
>>>> working computer as well).
>>>> 
>>>> Is there anything I can try to debug this?
>>> 
>>> Hi, I commented on your StackOverflow question, great to see you here!
>>> 
>>> The only thing you can add is --debug. That will make Mercurial print
>>> some more information. I tested it here by adding
>>> 
>>> [paths]
>>> foo = http://foobar
>>> 
>>> [http_proxy]
>>> host = no-such-host
>>> 
>>> to a .hg/hgrc file and then I get:
>>> 
>>> $ incoming foo --debug
>>> using http://foobar/
>>> proxying through http://no-such-host:None
>>> sending capabilities command
>>> abort: error: Name or service not known
>>> 
>>> That shows me that
>>> 
>>> 1) the foo is correctly expanded to a HTTP URL
>>> 2) the proxy config is read and hg tries to use it
>>> 
>>> --
>>> Martin Geisler
>>> 
>>> aragost Trifork
>>> Professional Mercurial support
>>> http://mercurial.aragost.com/kick-start/
>>> 
>> 
>> 
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial




More information about the Mercurial mailing list