Thread (5 messages) flat view 5 messages, 2 authors, 2016-06-15

Re: Access to git repository through squid proxy: The remote end hung up unexpectedly

From: Konstantin Khomoutov <hidden>
Date: 2016-06-15 22:52:36

On Sat, 10 Dec 2011 09:56:07 +0100
Mathieu Peltier [off-list ref] wrote:
Hi,
I am trying to access a git repository (git:// URL) through a squid
proxy.

squid allows CONNECT for port 9418:
[...]
2011/12/09 12:22:44 socat[21428] D shutdown()  -> 0
fatal: The remote end hung up unexpectedly

I tried to use also nc but I get the same error.
Any advice?
I think you have to verify the git-daemon (you did not say you're using
git-daemon, but it can be presupposed based on the port number) works
by itself before starting to wrap it into layers of complexity.
What happens if you try to clone a git repo directly, without any
tunneling?  If this is not possible, try to clone on the host running
git-daemon (use an URL like git://localhost/path/to/repo.git).
If it fails (I suppose it will), try increasing the daemon verbosity
(see git-daemon) manpage.
After all, may be it's as simple as forgetting to `touch` git-export-ok
file in the repository you're trying to clone.

P.S.
As a side note: why are you trying to implement such a strange setup?
Why not just use plain old SSH which just works and provides good level
of security (contrary to Basic HTTP authentication you might be using).
If you need a level of control about who can do what with the repository
you could look at https://github.com/sitaramc/gitolite
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help