mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: "Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Git via a proxy server?
Date: Thu, 23 Feb 2006 17:10:10 +0300	[thread overview]
Message-ID: <20060223171010.283a9bfe.vsu@altlinux.ru> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F022DD553@otce2k03.adaptec.com>

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

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.

Note: most HTTP proxy servers allow CONNECT method to a very limited
range of ports, and administrators will need to enable the git port
(9418) explicitly.

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2006-02-23 14:10 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 [this message]
2006-02-26 23:35   ` [OT] " Petr Vandrovec

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=20060223171010.283a9bfe.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    /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