RE: Commit 5841520b makes it impossible to connect to github from behind my company's firewall.

From: Junio C Hamano [mailto:jch2...@gmail.com] On Behalf Of Junio C Hamano [administrivia: please do not cull people out of the Cc: list] Johan Laenen writes: > Enrique Tobis twosigma.com> writes: > >> There is something I don't understand, though. Johan must be >

RE: Commit 5841520b makes it impossible to connect to github from behind my company's firewall.

From: Junio C Hamano [mailto:jch2...@gmail.com] On Behalf Of Junio C Hamano > Enrique Tobis writes: >> Hey! >> >> I'm really sorry to hear that. >> >> That change should enable more forms of authentication with your >> proxy, but it does c

RE: Commit 5841520b makes it impossible to connect to github from behind my company's firewall.

your proxy use? Thanks, Enrique -Original Message- From: Matthieu Moy [mailto:matthieu@grenoble-inp.fr] Sent: Tuesday, October 20, 2015 07:46 To: Johan Laenen Cc: git@vger.kernel.org; Enrique Tobis Subject: Re: Commit 5841520b makes it impossible to connect to github from behind my comp

RE: [PATCH] http: always use any proxy auth method available

Thanks for your feedback! > -Original Message- > From: Junio C Hamano [mailto:jch2...@gmail.com] On Behalf Of Junio C > Hamano > Sent: Friday, June 26, 2015 15:25 > To: Enrique Tobis > Cc: 'git@vger.kernel.org'; 'Nelson Benitez Leon' > Subject: Re

[PATCH] http: always use any proxy auth method available

By default, libcurl honors some environment variables that specify a proxy (e.g. http_proxy, https_proxy). Also by default, libcurl will only try to authenticate with a proxy using the Basic method. This change makes libcurl always try the most secure proxy authentication method available. As a con