From: Petr Vandrovec <petr@vmware.com>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [OT] Re: Git via a proxy server?
Date: Mon, 27 Feb 2006 00:35:00 +0100 [thread overview]
Message-ID: <44023B24.9070100@vmware.com> (raw)
In-Reply-To: <20060223171010.283a9bfe.vsu@altlinux.ru>
Sergey Vlasov wrote:
> On Wed, 22 Feb 2006 10:44:23 -0500 Salyzyn, Mark wrote:
>
>
>>Rsync protocol for git is not working for some reason when I pick up the
>>trees; apparently others share my experience. So I switched to the git
>>protocol. I can pick up the trees via git if I am outside Adaptec's
>>network, but inside I need to go through the proxy server.
>
>
> I have successfully used transconnect
> (http://sourceforge.net/projects/transconnect) for tunnelling git
> protocol through a HTTP proxy (squid in my case) supporting the CONNECT
> method.
>
> Git also supports the GIT_PROXY_COMMAND environment variable (or
> core.gitproxy config option), through which you can specify a program to
> be run instead of connecting to a TCP port - then you can use netcat for
> connecting through proxy; however, I have not tried this.
I know I'm comming kinda late, but I'm using:
export GIT_PROXY_COMMAND=/usr/local/bin/proxy-cmd.sh
and proxy-cmd.sh is just single-line command glued from what I found
available in /bin:
#! /bin/bash
(echo "CONNECT $1:$2 HTTP/1.0"; echo; cat ) | socket
proxy.ourcompany.com 3128 | (read a; read a; cat )
Replace socket's arguments 'proxy.ourcompany.com 3128' with your http
proxy. Fortunately our proxy does not see anything wrong with git's port.
Best regards,
Petr Vandrovec
prev parent reply other threads:[~2006-02-26 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 15:44 Salyzyn, Mark
2006-02-22 19:22 ` Anderson Lizardo
2006-02-23 14:10 ` Sergey Vlasov
2006-02-26 23:35 ` Petr Vandrovec [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44023B24.9070100@vmware.com \
--to=petr@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=vsu@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome