[yocto] Git clone over http broken on git.yoctoproject.org

[Michael_E_Brown at Dell.com]

Local cntlm proxy pointing at corporate MS proxy. I tried two git versions. One is the base git version in CentOS 6.3, the other from the yocto 1.5 buildtools tarball. It looks like the newer git version works and the older one does not. I'll just use A) the newer git version, and B) https.

Base CentOS version:

$ git --version
git version 1.7.1
$ git clone http://git.yoctoproject.org/git/poky.git
Initialized empty Git repository in /home/michael_e_brown/yocto/poky/.git/
error: RPC failed; result=52, HTTP code = 100

Yocto 1.5 buildtools version:

$ git --version
git version 1.8.3.4
$ git clone http://git.yoctoproject.org/git/poky.git
Cloning into 'poky'...
remote: Counting objects: 215358, done.
remote: Compressing objects: 100% (54081/54081), done.
remote: Total 215358 (delta 156744), reused 215022 (delta 156422)
Receiving objects: 100% (215358/215358), 98.12 MiB | 836.00 KiB/s, done.
Resolving deltas: 100% (156744/156744), done.
Checking connectivity... done

Looks like newer git works ok.
--
Michael
________________________________________
From: Daniel Stenberg [daniel at haxx.se]
Sent: Friday, December 13, 2013 8:46 AM
To: Brown, Michael E
Cc: michael at yoctoproject.org; yocto at yoctoproject.org
Subject: Re: [yocto] Git clone over http broken on git.yoctoproject.org

On Thu, 12 Dec 2013, Michael_E_Brown at Dell.com wrote:

> HOWEVER, if I use "https" instead of "http", it all WORKS OK. NOTE: Some
> repos work over http, some don't. Working: meta-selinux, yocto-autobuilder,
> for example.

You're using a HTTP proxy, right? I suspect the http vs https difference is
then simply because git will use completely different ways to go through the
proxies for the different protocols.

> git clone --mirror http://git.yoctoproject.org/git/poky.git
> Initialized empty Git repository in /home/michael_e_brown/yocto/poky.git/
> error: RPC failed; result=52, HTTP code = 100

I think this means that git gets a HTTP 100 continue response back but then
nothing else, which indicates a problem in your network or proxy.

Can you use git fine over this http+proxy against other git repos out in the
wild? Which git + libcurl versions are you using?

--

  / daniel.haxx.se