From: Johan Laenen <johan.laenen+cygwin@gmail.com>
To: git@vger.kernel.org
Subject: Commit 5841520b makes it impossible to connect to github from behind my company's firewall.
Date: Tue, 20 Oct 2015 11:20:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20151020T131513-529@post.gmane.org> (raw)
Commit 5841520b makes it impossible to connect to github from behind my
company's firewall.
I'm running CYGWIN_NT-6.1 and the default git version 2.5.3 complains with a
fatal error when trying to git pull:
$ /bin/git --version
git version 2.5.3
$ /bin/git pull
fatal: unable to access 'https://github.com/gargle/french/': Unknown SSL
protocol error in connection to github.com:443
Taking the sources of git 2.6.1. and compiling with commit 5841520b in
http.c reverted gives me a working git.
My http.c now looks like:
466 if (curl_http_proxy) {
467 curl_easy_setopt(result, CURLOPT_PROXY, curl_http_proxy);
468 #if LIBCURL_VERSION_NUM >= 0x070a07
469 curl_easy_setopt(result, CURLOPT_PROXYAUTH, CURLAUTH_ANY);
470 #endif
471 }
And it works:
$ git --version
git version 2.6.1
$ git pull
Already up-to-date.
Greetings,
Johan
next reply other threads:[~2015-10-20 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 11:20 Johan Laenen [this message]
2015-10-20 11:46 ` Commit 5841520b makes it impossible to connect to github from behind my company's firewall 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
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.20151020T131513-529@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).