Re: git-fetch vs ipv6 routing issues

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: James Cloos
Date: Tuesday, June 3, 2008 - 12:53 pm

>>>>> "Daniel" == Daniel Stenberg <daniel@haxx.se> writes:


Daniel> Isn't this simply because libcurl (used for http) has no retry
Daniel> functionality on this scenario while git itself has that for the
Daniel> git protocol?

Yes, that is true.

But git could be smarter about it.  libcurl has CURLOPT_IPRESOLVE which
can be set to any of CURL_IPRESOLVE_WHATEVER, CURL_IPRESOLVE_V4 or
CURL_IPRESOLVE_V6.  Git could at least allow setting that via a config
option and/or an env var, just like it does for libcurl options like
CURLOPT_LOW_SPEED_LIMIT.

Even better would be to set CURLOPT_CONNECT_ONLY and then try with
CURL_IPRESOLVE_WHATEVER, CURL_IPRESOLVE_V6 and CURL_IPRESOLVE_V4 in turn
until it gets a connection, and then use CURLINFO_LASTSOCKET and the
full URL to do the GET.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git-fetch vs ipv6 routing issues, James Cloos, (Sat May 31, 10:56 am)
Re: git-fetch vs ipv6 routing issues, Daniel Stenberg, (Sun Jun 1, 12:25 am)
Re: git-fetch vs ipv6 routing issues, James Cloos, (Tue Jun 3, 12:53 pm)
Re: git-fetch vs ipv6 routing issues, Daniel Stenberg, (Tue Jun 3, 1:50 pm)
Re: git-fetch vs ipv6 routing issues, James Cloos, (Tue Jun 3, 4:56 pm)