On Fri, May 18, 2007 at 01:13:36PM -0700, Linus Torvalds wrote:
> 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.
With CONNECT, there isn't anything. That is, your
GIT_PROXY_COMMAND handles talking to the proxy, then gives git itself a
raw data pipe. My proxy allows CONNECT to 9418, and that's how I use it
today.
If you tried to make POST work (It'd be POST, not GET, as you
need to connect up the sending side), either apache would have to front
it for us, or "git-daemon --http" would have to accept the HTTP headers
on before the input, and output a proper HTTP response before sending
output. Seeing the headers would allow for us to vhost, even.
Hmm, but the proxy may not allow two-way communication. Does
the git protocol have more than one round-trip? That is:
Client:
POST http://server.git.host:80/projects/thisproject HTTP/1.1
Host: server.git.host
fetch-pack <sha1>
EOF
Server:
200 OK HTTP/1.1
<data>
EOF
should work, I'd think.
Joel
--
"Ninety feet between bases is perhaps as close as man has ever come
to perfection."
- Red Smith
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@xxxxxxxxxx
Phone: (650) 506-8127
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
