Unfortunately, I was unable to get git clone 
http://git.gitorious.org/webkit/webkit.git
to work properly,
however I was able to get git fetching with the git protocol behind
our firewall.
It requires your http proxy to be configured to allow HTTP CONNECT to
port 9418 (the standard git protocol port), so it may not work for
everyone.

I adapted these instructions from:
http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/
and changed them to use corkscrew instead of socat - as I already had
corkscrew handy due to configuring SSH to use it (
http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/ ).

Here's how:

Edit a new file ~/bin/gitproxy and put this content in it:
  #!/bin/sh

  # Use corkscrew 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 through port 9418
  #
  # Save this file as gitproxy somewhere in your path (e.g. ~/bin)
  # and then run:
  #   chmod +x gitproxy
  #   git config --global core.gitproxy gitproxy
  #
  # Adapted from http://tinyurl.com/8xvpny which uses socat instead of
corkscrew.

  _proxy=<your proxy ip here>
  _proxyport=<your proxy port here>
  exec corkscrew $_proxy $_proxyport $1 $2

Make sure that ~/bin is in your path, and that gitproxy is executable
(per comments in file).
Configure git to use this new proxy command via:
git config --global core.gitproxy gitproxy

and now, if your HTTP CONNECT proxy is configured to allow proxy
connections to port 9418, then you should be able to access git
repositories using the git:// protocol.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/gitorious?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to