Databases
StackOverflow2013
Postsdbo
POgit clone timed out when used through https proxy
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POgit clone timed out when used through https proxy
    text
    copied!<p>The command "git clone <a href="https://github.com/user/project.git">https://github.com/user/project.git</a>" times out when being used through an https proxy.</p> <p>I've successfully had git functioning behind a proxy before, and have read other stackoverflow related to git and proxy usage. Now I've configured it on a host in my current organization to use a non-authenticating proxy, but it's timing out.</p> <ul> <li>the proxy is squid, non-authenticating</li> <li>directly connecting via TCP-443 is not an option</li> <li>I've confirmed that git is contacting the proxy</li> <li>Git issues the command "CONNECT github.com:443 HTTP/1.1"</li> <li>The proxy allows the request and connects to github.com on port 443</li> <li>libcurl verifies github's cert and establishes an SSL connection (SSL_RSA_WITH_RC4_128_SHA)</li> <li>git proceeds to sit there, waiting for something that never happens</li> <li>timeout occurs</li> </ul> <p>Has anyone experienced this before? Have any tips?</p> <p>Here's the system version:</p> <pre><code>$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.4 (Santiago) </code></pre> <p>Here's the git version and update information (latest available in RH)</p> <pre><code>$ git --version git version 1.7.11.3 $ sudo yum check-update git Loaded plugins: downloadonly, rhnplugin, security This system is receiving updates from RHN Classic or RHN Satellite. </code></pre> <p>Here's the relevant environmental variables:</p> <pre><code>$ export | grep http declare -x http_proxy="http://proxy.hostname:3128/" declare -x https_proxy="http://proxy.hostname:3128/" </code></pre> <p>Here's my .gitconfig (for redundancy):</p> <pre><code>$ cat ~/.gitconfig [http] proxy = http://proxy.hostname:3128/ [https] proxy = http://proxy.hostname:3128/ </code></pre> <p>Here's an example of git running (and eventually timing out):</p> <pre><code>$ GIT_CURL_VERBOSE=1 GIT_DEBUG_LOOKUP=1 GIT_TRANSLOOP_DEBUG=1 GIT_TRANSPORT_HELPER_DEBUG=1 git clone https://github.com/user/project.git 2&gt;&amp;1 Cloning into 'project'... Debug: Remote helper: -&gt; capabilities Debug: Remote helper: Waiting... Debug: Remote helper: &lt;- fetch Debug: Got cap fetch Debug: Remote helper: Waiting... Debug: Remote helper: &lt;- option Debug: Got cap option Debug: Remote helper: Waiting... Debug: Remote helper: &lt;- push Debug: Got cap push Debug: Remote helper: Waiting... Debug: Remote helper: &lt;- Debug: Capabilities complete. Debug: Remote helper: Waiting... * Couldn't find host github.com in the .netrc file; using defaults * About to connect() to proxy proxy.hostname 3128 (#0) * Trying 10.22.74.73... * Connected to proxy.hostname (x.x.x.x) port 3128 (#0) * Establish HTTP proxy tunnel to github.com:443 &gt; CONNECT github.com:443 HTTP/1.1 Host: github.com:443 User-Agent: git/1.7.11.3 Proxy-Connection: Keep-Alive Pragma: no-cache &lt; HTTP/1.0 200 Connection established &lt; * Proxy replied OK to CONNECT request * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSL connection using SSL_RSA_WITH_RC4_128_SHA * Server certificate: * subject: CN=github.com,O="GitHub, Inc.",L=San Francisco,ST=California,C=US,serialNumber=C3268102,incorporationState=California,incorporationCountry=US,businessCategory=Private Organization * start date: May 27 00:00:00 2011 GMT * expire date: Jul 29 12:00:00 2013 GMT * common name: github.com * issuer: CN=DigiCert High Assurance EV CA-1,OU=www.digicert.com,O=DigiCert Inc,C=US * Connected to proxy.hostname (x.x.x.x) port 3128 (#0) </code></pre> <p>Here's the squid log:</p> <pre><code>1367957877.701 60148 x.x.x.x TCP_MISS/200 3765 CONNECT github.com:443 - DIRECT/204.232.175.90 - </code></pre> <p>So, what's going on here? Does anyone have any ideas?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload