All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2012, #09; Mon, 23)
Date: Tue, 24 Apr 2012 11:57:26 -0700	[thread overview]
Message-ID: <xmqqipgpgdpl.fsf@junio.mtv.corp.google.com> (raw)
In-Reply-To: <4F966F0C.6090504@seap.minhap.es> (Nelson Benitez Leon's message of "Tue, 24 Apr 2012 11:14:52 +0200")

Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es> writes:

> 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 ^^

When cre_url.protocol is "https", this looks at $ENV{"https_proxy"}, no?

    http://curl.haxx.se/docs/manpage.html#ENVIRONMENT

> so are you referring to something else ?

There may be some other things that break people's settings but
regarding PROXY, the above was wnat I was referring to.

  reply	other threads:[~2012-04-24 18:57 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
2012-04-24 18:57   ` Junio C Hamano [this message]
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=xmqqipgpgdpl.fsf@junio.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nelsonjesus.benitez@seap.minhap.es \
    /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.