From: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2012, #09; Mon, 23)
Date: Tue, 24 Apr 2012 11:14:52 +0200 [thread overview]
Message-ID: <4F966F0C.6090504@seap.minhap.es> (raw)
In-Reply-To: <xmqq8vhmhzpk.fsf@junio.mtv.corp.google.com>
On 04/24/2012 12:04 AM, Junio C Hamano wrote:
>
> * nl/http-proxy-more (2012-04-19) 7 commits
> - http: fix proxy password passing
> - http: fix proxy authentication
> - http: rename HTTP_REAUTH to HTTP_AUTH_RETRY
> - http: Avoid limit of retrying request only twice
> - http: handle proxy authentication failure (error 407)
> - http: handle proxy proactive authentication
> - http: try http_proxy env var when http.proxy config option is not set
>
I'm a bit lost with the state of this, I read your last discussion and
you sent patches to support a proxy url without the protocol part, I assume
that's done and apart from that there is a bug in the LIBCURL_VERSION which
is an easy fix I could send a patch for.
> The code to talk to http proxies learn to use the same credential
> API used to talk to the final http destinations. This still needs
> to peek into $ENV{HTTPS_PROXY}.
My original patch already peeked in HTTPS_PROXY env var, I post the
relevant part:
+ if (!curl_http_proxy) {
+ const char *env_proxy, *no_proxy;
+ char *env_proxy_var;
+ int read_http_proxy;
+ struct strbuf buf = STRBUF_INIT;
+ credential_from_url(&cre_url, url);
+ strbuf_addf(&buf, "%s_proxy", cre_url.protocol);
+ env_proxy_var = strbuf_detach(&buf, NULL);
+ env_proxy = getenv(env_proxy_var);
^^ HERE ^^
+ if (env_proxy) {
+ read_http_proxy = 1;
+ no_proxy = getenv("no_proxy");
+ if (no_proxy && (!strcmp("*", no_proxy) || strstr(no_proxy, cre_url.host)))
+ read_http_proxy = 0;
+
+ if (read_http_proxy)
+ curl_http_proxy = xstrdup(env_proxy);
+ }
+ free(env_proxy_var);
+ }
if (curl_http_proxy) {
so are you referring to something else ?
next prev parent reply other threads:[~2012-04-24 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 22:04 What's cooking in git.git (Apr 2012, #09; Mon, 23) Junio C Hamano
2012-04-24 9:14 ` Nelson Benitez Leon [this message]
2012-04-24 18:57 ` Junio C Hamano
2012-04-26 13:16 ` [PATCH] Try an uppercase version of $prot_proxy env var Nelson Benitez Leon
2012-04-26 13:08 ` Jeff King
2012-04-26 15:18 ` Junio C Hamano
2012-04-26 16:29 ` Nelson Benitez Leon
2012-04-27 8:12 ` Jeff King
2012-04-27 15:03 ` Junio C Hamano
2012-04-26 14:04 ` Junio C Hamano
2012-04-25 2:14 ` What's cooking (incremental) Junio C Hamano
2012-04-25 9:06 ` Thomas Rast
2012-04-25 15:17 ` 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=4F966F0C.6090504@seap.minhap.es \
--to=nelsonjesus.benitez@seap.minhap.es \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.