Re: https_proxy and libcurl

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 22, 2013, 21:55 UTC
Message-ID: <7v7gm0c8ub.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CABURp0qQ6tO0B4Ya6OStX59SJqG-Jx1F4g6MUL7tVwR_6VgDhw@mail.gmail.com>

Phil Hord <phil.hord@gmail.com> writes:

Show 11 quoted lines

> I have been unable to clone via http proxy because of a wrongly
> configured proxy setup in my lab.
>
> I had this env:
>
>     http_proxy=http://proxy.myco.com
>     https_proxy=https://proxy.myco.com
>
> The problem is that libcurl ignores the protocol part of the proxy
> url, and it defaults to port 1080. wget honors the protocol specifier,
> but it defaults to port 80 if none is given.

IIRC, the historical norm is to set these to <host>:<port>.

So many people mistakenly write them with <method>:// that some tools over time learned to strip and ignore that prefix, though.

> The fix was to specify the port explicitly, like this:
>
>     http_proxy=proxy.myco.com:80
>     https_proxy=proxy.myco.com:443

Yeah, that is the correct syntax to use. Is there anything you want Git to do to be more helpful?