Re: Smart fetch via HTTP?

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: May 18, 2007, 20:13 UTC
Message-ID: <alpine.LFD.0.98.0705181312060.3890@woody.linux-foundation.org>
In-Reply-To: <20070518190159.GS24644@ca-server1.us.oracle.com>

On Fri, 18 May 2007, Joel Becker wrote:

Show 7 quoted lines

> 
> 	It's not about packet scanning, it's about GET vs CONNECT.  If
> the proxy allows GET but not CONNECT, it's going to forward the HTTP
> protocol to the server, and git-daemon is going to see "GET /project
> HTTP/1.1" as its first input.  Now, perhaps we can cook that up behind
> some apache so that apache handles vhosting the URL, then calls
> git-daemon which can take the stdin.  So we'd be doing POST, not GET.

If it's _just_ the initial GET/CONNECT strings, yeah, we could probably easily make the git-daemon just ignore them. That shouldn't be a problem.

But if there's anything *else* required, it gets uglier much more quickly.

		Linus