{"thread":{"id":"12373","subject":"RE: FW: git via http protocol _and_ a proxy using NTLM authentication -- git 1.5.4.2 & curl 7.18.0","startedAt":"2008-02-28T22:04:02Z","lastAt":"2008-02-29T00:59:58Z","messageCount":2,"participants":["ken.fuchs@bench.com","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"70324","messageId":"AA28F077645B324881335614E4F7C428034C11@win-ex01.bench.com","threadId":"12373","inReplyTo":null,"subject":"RE: FW: git via http protocol _and_ a proxy using NTLM authentication -- git 1.5.4.2 & curl 7.18.0","fromName":"","fromEmail":"ken.fuchs@bench.com","sentAt":"2008-02-28T22:04:02Z","receivedAt":"2008-02-28T22:04:02Z","isPatch":false,"sender":{"key":"ken.fuchs@bench.com","avatar":null},"body":"On Wed, 27 Feb 2008, Johannes Schindelin wrote:\n\n> On Wed, 27 Feb 2008, Ken Fuchs wrote:\n> \n> [Ken did not say who said this:]\n\nSorry, Mike Hommey wrote the following on 27 Feb 2008:\n\n> > > git-clone is not a builtin yet. When it is (and a patch \n> > > has come for that), it will correctly use proxys.\n> > \n> > Is there a work-around for cloning a git repository via a proxy?\n\n> Yes.\n> \n> Just export \"http_proxy\".  AFAICT this works... See\n> \n>\nhttp://repo.or.cz/w/msysgit.git?a=commitdiff;h=257a62710c0253d940a59b6fb\n2f371afa84dcf56\n\n> for a working example.\n\nUnfortunately, this will not work because \"git clone\" is\nimplemented by git-clone.sh and has no support for dealing\nwith proxies at all.  Note that the example uses \"git fetch\"\nand not \"get clone\".\n\nSo it seems that git's http protocol via a proxy isn't completely\nsupported.  For example, \"git fetch\" works with a proxy, since\nit is implemented via a builtin (executable) which includes\nproxy support.\n\nAt least that is my understanding of Mike's comments above.\n\nThe only work-around for \"git clone\" that I'm aware of is a\n\"proxy agent\" that intercepts and modifies all Internet bound\nrequests and responses so they go (transparently) through the\nproxy server rather than directly to the Internet.  Thus, none\nof the clients being used need to be proxy aware, including\n\"git clone\" (or any git function for that matter).\n\nHowever, I was looking for a different work-around for\nusing \"git clone\" via http protocol and proxy (NTLM auth.),\nbut there do not appear to be any.\n\nThanks,\n\nKen Fuchs\n"},{"id":"70334","messageId":"alpine.LSU.1.00.0802290057230.22527@racer.site","threadId":"12373","inReplyTo":"AA28F077645B324881335614E4F7C428034C11@win-ex01.bench.com","subject":"RE: FW: git via http protocol _and_ a proxy using NTLM authentication -- git 1.5.4.2 & curl 7.18.0","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-02-29T00:59:58Z","receivedAt":"2008-02-29T00:59:58Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 28 Feb 2008, Ken.Fuchs@bench.com wrote:\n\n> On Wed, 27 Feb 2008, Johannes Schindelin wrote:\n> \n> > On Wed, 27 Feb 2008, Ken Fuchs wrote:\n> > \n> > [Ken did not say who said this:]\n> \n> Sorry, Mike Hommey wrote the following on 27 Feb 2008:\n> \n> > > > git-clone is not a builtin yet. When it is (and a patch \n> > > > has come for that), it will correctly use proxys.\n> > > \n> > > Is there a work-around for cloning a git repository via a proxy?\n> \n> > Yes.\n> > \n> > Just export \"http_proxy\".  AFAICT this works... See\n> > \n> >\n> http://repo.or.cz/w/msysgit.git?a=commitdiff;h=257a62710c0253d940a59b6fb\n> 2f371afa84dcf56\n> \n> > for a working example.\n> \n> Unfortunately, this will not work because \"git clone\" is\n> implemented by git-clone.sh and has no support for dealing\n> with proxies at all.\n\nI fail to see why git-clone.sh, which uses git http-fetch directly, should \nbehave differently from git fetch, which uses git http-fetch directly.\n\nI strongly suspect that you did not even try what I suggested.\n\n> So it seems that git's http protocol via a proxy isn't completely \n> supported.\n\nIf that should really be the case, well, Git is a programmers' tool, so \nyou should be perfectly able to find out what is happening _exactly_.\n\nIf not, well, I heard subversion and Mercurial have nice Windows support.\n\nCiao,\nDscho\n\n"}]}