I was trying to clone the thrift repository at a clients office when this problem occurred.
Upon some Googling, I got this really useful link (thanks to Emil Sit)
which explained how git can be used over an http proxy for those git servers
which don’t allow http method as an alternate/bypass to the git protocol.
Okay, so here’s what’s needed to be done;
- Typed in the below lines (quoted) into a shell script called git-proxy and put it in $(HOME)/bin directory.
Of course; its executable bits has to be set with: chmod a+x $(HOME)/bin/git-proxy.123456789101112131415
# Use socat to proxy git through an HTTP CONNECT firewall.
# Useful if you are trying to clone git:// from inside a company.
# Requires that the proxy allows CONNECT to port 9418.
# Save this file as gitproxy somewhere in your path
# (e.g., ~/bin) and then run
# chmod +x git-proxy
# git config --global core.gitproxy git-proxy
# Configuration. Common proxy ports are 3128, 8123, 8000.
socat STDIO PROXY:$_proxy:$1:$2,proxyport=$_proxyport
Note: I replaced proxy.yourcompany.com with appropriate proxy-server details
for my organization and the value for _proxyport with an appropriate value
used in my organization (instead of the default 3128).
- Installed the package socat with the command; sudo apt-get install socat
- Ran the command git config –global core.gitproxy git-proxy to configure ‘git’ to use the git-proxy.
- With the http_proxy environment variable already set using:
I could now use git and get the repositories without any problems.