git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Cannot clone the git repository shared over http with authorization.

From
Clemens Buchacher <drizzd@aon.at>
Date
Apr 1, 2012, 19:45 UTC
Message-ID
<20120401194534.GA16512@ecki>
In-Reply-To
<20120401184804.GJ3236@szczaw.snafu.pl>
On Sun, Apr 01, 2012 at 08:48:04PM +0200, Artur R. Czechowski wrote:
Show 8 quoted lines
> 
> 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
Previous: Artur R. CzechowskiNext: Clemens Buchacher
Message 2 of 12 in “Cannot clone the git repository shared over http with authorization.”
  1. Artur R. CzechowskiApr 1, 2012
  2. Clemens BuchacherApr 1, 2012
  3. Clemens BuchacherApr 1, 2012
  4. Jeff KingApr 2, 2012
  5. Clemens BuchacherApr 10, 2012
  6. 1/2 http auth fails with multiple curl handlesClemens Buchacher, Apr 10, 2012
  7. 2/2 fix http auth with multiple curl handlesClemens Buchacher, Apr 10, 2012
  8. Jeff KingApr 12, 2012
  9. Junio C HamanoApr 12, 2012
  10. Jeff KingApr 13, 2012
  11. 1/2 http: clean up leak in init_curl_http_authJeff King, Apr 13, 2012
  12. 2/2 http: use newer curl options for setting credentialsJeff King, Apr 13, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.