git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: HTTP pushes

From
Junio C Hamano <junkio@cox.net>
Date
Nov 2, 2005, 00:36 UTC
Message-ID
<7v1x1z51id.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0511012008310.11979@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 7 quoted lines
> On Mon, 31 Oct 2005, Nick Hengeveld wrote:
>
>> HTTP is currently listed as a read-only/unsupported method for doing
>> pushes, is that due to inherent problems with HTTP or just because
>> it hasn't been written yet?
>> 
>> I've built a working prototype of an HTTP push implementation using DAV.

I had an impression that DAV has its own notion of version control, so using git as a backend on the server side might be an interesting exercise.

> I think this is useful. There are restrictive firewalls out there, which 
> only allow ports 80 and 443 to be connected to. Your work would fit in 
> right there.

Another solution for this would be to allow connect.c to use a HTTP connect passthru proxy. CVS does this with an ugly but easy to understand notation:

    ':pserver;proxy=firewall;proxyport=3128:user@host:/path/to/repo
Previous: Johannes SchindelinNext: David Lang
Message 3 of 8 in “HTTP pushes”
  1. Nick HengeveldNov 1, 2005
  2. Johannes SchindelinNov 1, 2005
  3. Junio C HamanoNov 2, 2005
  4. David LangNov 2, 2005
  5. Nick HengeveldNov 2, 2005
  6. Johannes SchindelinNov 2, 2005
  7. Daniel BarkalowNov 1, 2005
  8. H. Peter AnvinNov 3, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.