From: Junio C Hamano <gitster@pobox.com>
To: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
Cc: git@vger.kernel.org, peff@peff.net, sam@vilain.net
Subject: Re: [PATCH v2 2/3] http: try http_proxy env var when http.proxy config option is not set
Date: Thu, 01 Mar 2012 11:10:38 -0800 [thread overview]
Message-ID: <7vy5rkm91t.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4F4FBE0F.6020004@seap.minhap.es> (Nelson Benitez Leon's message of "Thu, 01 Mar 2012 19:21:03 +0100")
Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es> writes:
> CuRL already reads it, but if $http_proxy has username but no password
> curl will not ask you for the password.. so we read it ourselves to
> detect that and ask for the password.
Please stop the double-dot. Also your capitalization for cURL is screwed
up.
More importantly, please describe what happens after "will not ask".
"will not ask you for the password and the connection fails"?
"will not ask you for the password and the gives an error message saying
'authentication failure'"?
The logic in the patch, needless to say, seems OK, though.
Thanks.
>
> Signed-off-by: Nelson Benitez Leon <nbenitezl@gmail.com>
> ---
> http.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/http.c b/http.c
> index 8ac8eb6..8932da5 100644
> --- a/http.c
> +++ b/http.c
> @@ -295,6 +295,13 @@ static CURL *get_curl_handle(void)
> if (curl_ftp_no_epsv)
> curl_easy_setopt(result, CURLOPT_FTP_USE_EPSV, 0);
>
> + if (!curl_http_proxy) {
> + const char *env_proxy;
> + env_proxy = getenv("http_proxy");
> + if (env_proxy) {
> + curl_http_proxy = xstrdup(env_proxy);
> + }
> + }
> if (curl_http_proxy) {
> curl_easy_setopt(result, CURLOPT_PROXY, curl_http_proxy);
> curl_easy_setopt(result, CURLOPT_PROXYAUTH, CURLAUTH_ANY);
next prev parent reply other threads:[~2012-03-01 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 18:21 [PATCH v2 2/3] http: try http_proxy env var when http.proxy config option is not set Nelson Benitez Leon
2012-03-01 17:45 ` Sam Vilain
2012-03-01 18:33 ` Junio C Hamano
2012-03-01 19:10 ` Junio C Hamano [this message]
2012-03-01 21:01 ` Jeff King
2012-03-01 21:38 ` Junio C Hamano
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=7vy5rkm91t.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nelsonjesus.benitez@seap.minhap.es \
--cc=peff@peff.net \
--cc=sam@vilain.net \
/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).