git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam.vilain@catalyst.net.nz>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, francois@debian.org
Subject: Re: [PATCH] Allow HTTP proxy to be overridden in config
Date: Fri, 23 Nov 2007 16:35:44 +1300	[thread overview]
Message-ID: <47464A90.4030509@catalyst.net.nz> (raw)
In-Reply-To: <7voddl24b7.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
>> The http_proxy / HTTPS_PROXY variables used by curl to control
>> proxying may not be suitable for git.  Allow the user to override them
>> in the configuration file.
>> ---
>>   In particular, privoxy will block directories called /ad/ ... d'oh!
>> +++ b/Documentation/config.txt
>> +http.proxy::
>> +	Override the HTTP proxy, normally configured using the 'http_proxy'
>> +	environment variable (see gitlink:curl[1]).
> 
> This may work around the issue you cited, but it makes me wonder
> if it is a road to insanity.  Does the curl library expect that
> (1) each and every HTTP talking application that uses the
> library offer this kind of knob for its users to tweak, and (2)
> users set the knob for each and every one of such application?

This is true.  However I still think that it is a useful feature for
many users, with few side effects.  If nothing else the bit on the man
page will prompt them to think, "oh, I should set that in the environment".

> I would say if privoxy cannot be tweaked to allow /ad/ in chosen
> context (e.g. /ad/ in general is rejected but /objects/ad/ is
> Ok), that is what needs to be fixed.
> Or it would be the use of such a broken proxy by the user.  That
> can be fixed and much easily.

Yes - but consider the dilemma of the user.  They've apt-get installed
this privoxy thing and figured out how to set their applications to use
it.  Now, it doesn't work and they think it is the proxy in the way, and
they've no idea that they might be able to reconfigure it.  This way
they can tell git to bypass it.

I don't know, I see your point and pretty much agree with it.  It just
seems like something that might come in handy (as well as be another
vector for something you need to check when you get HTTP fetch issues -
so maybe a command-line option would be better).

Actually something that would really have helped is more documentation
of the various GIT_CURL_* environment variables available for debugging.
-- 
Sam Vilain, Chief Yak Shaver, Catalyst IT (NZ) Ltd.
phone: +64 4 499 2267        PGP ID: 0x66B25843

  reply	other threads:[~2007-11-23  4:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  0:07 [PATCH] Allow HTTP proxy to be overridden in config Sam Vilain
2007-11-23  0:28 ` Junio C Hamano
2007-11-23  3:35   ` Sam Vilain [this message]
2007-12-01  2:37     ` Junio C Hamano
2007-12-03  9:09       ` Andreas Ericsson
2007-12-03 11:13         ` Johannes Schindelin
2007-12-03 21:48       ` Sam Vilain
2007-12-04  8:49         ` Junio C Hamano
2007-12-04  9:22           ` Sam Vilain

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=47464A90.4030509@catalyst.net.nz \
    --to=sam.vilain@catalyst.net.nz \
    --cc=francois@debian.org \
    --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 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).