From: Graham Barr <gbarr@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Grégoire Barbier" <gb@gbarbier.org>, git@vger.kernel.org
Subject: Re: git over webdav: what can I do for improving http-push ?
Date: Mon, 31 Dec 2007 10:57:52 -0600 [thread overview]
Message-ID: <47791F90.8030302@pobox.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0712302145500.13593@iabervon.org>
Daniel Barkalow wrote:
> On Sun, 30 Dec 2007, Grégoire Barbier wrote:
>> I'm using Git for a rather short time but enough to fall in love with it. For
>> a few days I'm trying to use it over webdav, that is over http/https with
>> write (push) access. As for me, the main rationale to use http(s) rather than
>> git or ssh is to get through corporate firewalls, otherwise I would probably
>> not bother with webdav.
> In general, we've been able to either get through firewalls with ssh or
> it's all in the same VPN. So it's kind of unloved at this point. People
> poke at it occasionally, but mostly in the context of other fixes, I
> think.
If you have a http proxy that you can use, the you can use ssh via that with
something like corkscrew. http://wiki.kartbuilding.net/index.php/Corkscrew_-_ssh_over_https
A simple shell script wrapper around ssh to detect when you are behind a firewall
can inject the ProxyCommand into the command line arguments with -o
Graham.
next prev parent reply other threads:[~2007-12-31 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 22:59 git over webdav: what can I do for improving http-push ? Grégoire Barbier
2007-12-31 3:46 ` Daniel Barkalow
2007-12-31 16:57 ` Graham Barr [this message]
2008-01-01 11:33 ` Jan Hudec
2008-01-01 11:41 ` Grégoire Barbier
2008-01-01 18:12 ` Jakub Narebski
2008-01-01 20:23 ` Jan Hudec
2008-01-03 19:14 ` Grégoire Barbier
2008-01-03 21:15 ` Jan Hudec
2008-01-03 21:43 ` Linus Torvalds
2008-01-03 21:47 ` Jakub Narebski
2008-01-03 23:29 ` Grégoire Barbier
2008-01-03 23:54 ` Martin Langhoff
2008-01-04 19:59 ` Jan Hudec
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=47791F90.8030302@pobox.com \
--to=gbarr@pobox.com \
--cc=barkalow@iabervon.org \
--cc=gb@gbarbier.org \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).