From: Junio C Hamano <gitster@pobox.com>
To: Sam Vilain <sam.vilain@catalyst.net.nz>
Cc: git@vger.kernel.org, francois@debian.org
Subject: Re: [PATCH] Allow HTTP proxy to be overridden in config
Date: Thu, 22 Nov 2007 16:28:28 -0800 [thread overview]
Message-ID: <7voddl24b7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1195776420-22075-1-git-send-email-sam.vilain@catalyst.net.nz> (Sam Vilain's message of "Fri, 23 Nov 2007 13:07:00 +1300")
Sam Vilain <sam.vilain@catalyst.net.nz> writes:
> 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!
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 7ee97df..859a7f3 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -515,6 +515,10 @@ specified as 'gitcvs.<access_method>.<varname>' (where 'access_method'
> is one of "ext" and "pserver") to make them apply only for the given
> access method.
>
> +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?
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.
next prev parent reply other threads:[~2007-11-23 0:28 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 [this message]
2007-11-23 3:35 ` Sam Vilain
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=7voddl24b7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=francois@debian.org \
--cc=git@vger.kernel.org \
--cc=sam.vilain@catalyst.net.nz \
/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).