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

Re: DNS issue when cloning over HTTP and HTTPS

From
Daniel Stenberg <daniel@haxx.se>
Date
Jun 17, 2013, 22:45 UTC
Message-ID
<alpine.DEB.2.00.1306180038490.19414@tvnag.unkk.fr>
In-Reply-To
<20130617222356.GA22255@admin.romednet.com>
On Tue, 18 Jun 2013, LCD 47 wrote:
Show 9 quoted lines
>    Cloning with the git protocol works as expected.
>
> A search on the net shows people having the same problem more than an year 
> ago, and the solution there seems to imply that Git can't cope with async 
> DNS in curl:
>
> http://osdir.com/ml/freebsd-ports-bugs/2012-05/msg00095.html
>
>    Any idea?

It's not a git problem really. When you build libcurl to use c-ares for asynch name resolving you unfortunately don't get a really feature complete replacement for all stuff the stock synch resolver can do and I believe you (and person from that link from last year) experience that.

The solution for you is to:

a) rebuild libcurl with another resolving backend (there's a synch and threaded asynch one to choose from)

  or
b) fix c-ares to work "properly" in this scenario as well
-- 
  / daniel.haxx.se
Previous: LCD 47Next: LCD 47
Message 2 of 3 in “DNS issue when cloning over HTTP and HTTPS”
  1. LCD 47Jun 17, 2013
  2. Daniel StenbergJun 17, 2013
  3. LCD 47Jun 17, 2013

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.