From: Darrin Thompson <darrint@progeny.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: git@vger.kernel.org
Subject: Re: Using git with http behind proxy with authentification?
Date: Mon, 25 Jul 2005 17:14:33 -0500 [thread overview]
Message-ID: <1122329673.4378.4.camel@localhost.localdomain> (raw)
In-Reply-To: <42E21A33.6010804@de.bosch.com>
On Sat, 2005-07-23 at 12:21 +0200, Dirk Behme wrote:
> In the past, for bk I used
>
> $ export http_proxy=http://user:password@someproxy.some.where:8080/
>
> which worked. But no luck with cogito/git.
>
> Looking into recent cogito/git, the reason for this seems to be that
> cogito/git uses a combination of wget in scripts and curl in compiled
> executables. Having a look to cg-pull script, this script uses wget.
> Then, it calls git-http-pull if it thinks that http should be used.
> Looking at http-pull.c shows that there curl is used for http access. If
> I understand it correctly from man pages, wget understands user:password
> syntax of http_proxy environment, but curl doesn't. As I understand it
> curl understands only 'someproxy.some.where:8080' and wants the user and
> password given as parameter of curl_easy_setopt. The curl_easy_setopt
> man page tells something about CURLOPT_PROXYUSERPWD parameter.
>
For git itself everything is curl only now as far as I know. That's new
as of hours after you sent this.
Git turns on .netrc for doing 401 http auth. I wonder if curl will
consult .netrc for 407 proxy credentials as well?
Somebody would have to read code and/or try it.
--
Darrin
prev parent reply other threads:[~2005-07-25 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 10:21 Using git with http behind proxy with authentification? Dirk Behme
2005-07-25 22:14 ` Darrin Thompson [this message]
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=1122329673.4378.4.camel@localhost.localdomain \
--to=darrint@progeny.com \
--cc=dirk.behme@de.bosch.com \
--cc=git@vger.kernel.org \
/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.