From: Clemens Buchacher <drizzd@aon.at>
To: "Artur R. Czechowski" <arturcz@hell.pl>
Cc: git@vger.kernel.org
Subject: Re: Cannot clone the git repository shared over http with authorization.
Date: Sun, 1 Apr 2012 21:45:36 +0200 [thread overview]
Message-ID: <20120401194534.GA16512@ecki> (raw)
In-Reply-To: <20120401184804.GJ3236@szczaw.snafu.pl>
On Sun, Apr 01, 2012 at 08:48:04PM +0200, Artur R. Czechowski wrote:
>
> arturcz@szczaw:/tmp$ git clone http://blabluga.hell.pl/git/test.git
> Cloning into 'test'...
> error: The requested URL returned error: 401 (curl_result = 22, http_code = 401, sha1 = e884293079beab9f2583b59b4e05479fc84fc588)
> error: Unable to find e884293079beab9f2583b59b4e05479fc84fc588 under http://blabluga.hell.pl/git/test.git
> Cannot obtain needed commit e884293079beab9f2583b59b4e05479fc84fc588
> while processing commit c64bcf957545f61436d405326d985521dc45058f.
> error: Fetch failed.
I've been looking at this a bit. It's probably worth mentioning that the
problem does _not_ happen if username and password are specified in the
URL or in the .netrc. In both of those cases, curl is taking care of the
credentials itself.
So far I figured out that setting 'git config http.maxRequests 1' fixes
the problem as well. Looking at the output with GIT_CURL_VERBOSE=1 set,
it seems that some GET requests use the credentials, while others do
not. My guess is that the CURLOPT_USERPWD option does not apply to all
threads.
Clemens
next prev parent reply other threads:[~2012-04-01 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 18:48 Cannot clone the git repository shared over http with authorization Artur R. Czechowski
2012-04-01 19:45 ` Clemens Buchacher [this message]
2012-04-01 20:53 ` Clemens Buchacher
2012-04-02 8:31 ` Jeff King
2012-04-10 9:53 ` Clemens Buchacher
2012-04-10 9:53 ` [PATCH 1/2] http auth fails with multiple curl handles Clemens Buchacher
2012-04-10 9:53 ` [PATCH 2/2] fix http auth " Clemens Buchacher
2012-04-12 7:09 ` Jeff King
2012-04-12 22:50 ` Junio C Hamano
2012-04-13 6:16 ` Jeff King
2012-04-13 6:18 ` [PATCH 1/2] http: clean up leak in init_curl_http_auth Jeff King
2012-04-13 6:19 ` [PATCH 2/2] http: use newer curl options for setting credentials Jeff King
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=20120401194534.GA16512@ecki \
--to=drizzd@aon.at \
--cc=arturcz@hell.pl \
--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 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).