From: Johan Laenen <johan.laenen+cygwin@gmail.com>
To: git@vger.kernel.org
Subject: Re: Commit 5841520b makes it impossible to connect to github from behind my company's firewall.
Date: Wed, 21 Oct 2015 07:19:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20151021T091641-32@post.gmane.org> (raw)
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
next prev parent reply other threads:[~2015-10-21 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 11:20 Commit 5841520b makes it impossible to connect to github from behind my company's firewall Johan Laenen
2015-10-20 11:46 ` Matthieu Moy
2015-10-20 13:39 ` Enrique Tobis
2015-10-20 14:23 ` Johan Laenen
2015-10-20 14:30 ` Johan Laenen
2015-10-20 16:11 ` Junio C Hamano
2015-10-20 17:06 ` Enrique Tobis
2015-10-21 5:34 ` Johan Laenen
2015-10-21 7:19 ` Johan Laenen [this message]
2015-10-21 18:29 ` Junio C Hamano
2015-10-21 18:45 ` Enrique Tobis
-- strict thread matches above, loose matches on Subject: below --
2015-10-21 6:09 Johan Laenen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20151021T091641-32@post.gmane.org \
--to=johan.laenen+cygwin@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).