From: Johan Laenen <johan.laenen+cygwin@gmail.com>
Date: Wed, 21 Oct 2015 07:19:40 GMT
Subject: Re: Commit 5841520b makes it impossible to connect to github from behind my company's firewall.
Message-ID: <loom.20151021T091641-32@post.gmane.org>
In-Reply-To: <33632f538b4a406fb8f0e1eb2b016c43@EXMBNJE8.ad.twosigma.com>

Enrique Tobis <Enrique.Tobis <at> twosigma.com> writes:

> There is something I don't understand, though. Johan must be configuring
his proxy either a) through git
> config files; or b) through environment variables. Johan says his proxy
uses NTLM authentication. If he
> is doing a), then my change should not have had any impact. We were
already setting CURLOPT_PROXYAUTH to
> CURLAUTH_ANY in that case. If it's b), then his proxy couldn't have been
using NTLM authentication. In the
> old code path, only _BASIC was available as an authentication mechanism.
That default is what prompted me
> to make the change in the first place.

Interesting!

I tried both git versions, the one with the revert of commit 5841520b and
the one without and both gave me the fatal error "Unknown SSL protocol error
in connection to github.com:443" when using the ~/.gitconfig [https] and
[http] proxy settings instead of using the https_proxy environment variable.

Greetings,

Johan