Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Git does not appear to support authenticated proxy servers. You can check <a href="http://git.kernel.org/?p=git/git.git;a=blob;f=http.c;hb=HEAD" rel="nofollow noreferrer"><code>http.c</code> from the git.git repository</a>; in order to support authenticated proxy servers at all, it would have to set <a href="http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#CURLOPTPROXYUSERPWD" rel="nofollow noreferrer"><code>CURL_PROXYUSERPWD</code></a> to set the username and password, but that string does not appear in that file.</p> <p>One possible solution would be to fix Git; add a few more configuration parameters to <code>http.c</code>, such as <code>http.proxyuser</code>, <code>http.proxypass</code>, to set the username and password for the proxy, and <code>http.proxyauth</code> to set the authentication method, and then pass those in as the appropriate <a href="http://curl.haxx.se/libcurl/c/curl_easy_setopt.html" rel="nofollow noreferrer">cURL configuration options</a>.</p> <p>If you don't feel like hacking on the Git source code, you could set up your own, local proxy server, that needs no authentication, and then forward from that to the proxy server that requires authentication. <s><a href="http://www.squid-cache.org/" rel="nofollow noreferrer">Squid</a> supports <a href="http://www.squid-cache.org/Doc/config/cache_peer/" rel="nofollow noreferrer">this mode of operation</a>, though the configuration can be a little complex; I found <a href="http://nongraphical.com/2008/11/updated-squid-3-configuration/" rel="nofollow noreferrer">an example configuration</a> that purports to demonstrate this setup, though I haven't verified that it works myself.</s></p> <p><strong>edit</strong>: Never mind, after checking the <a href="http://www.google.com/codesearch/p?hl=en#GUxBL_cNJpE/src/http.c&amp;q=package:squid%20%22-%3Elogin%22%20package:%22cvs%20:pserver:anoncvs@cvs.squid-cache.org:/squid%20squid%22&amp;sa=N&amp;cd=5&amp;ct=rc&amp;l=1167" rel="nofollow noreferrer">Squid source code</a>, it appears to only support Basic authentication, not Digest authentication, when forwarding requests to a peer:</p> <pre><code>httpHeaderPutStrf(hdr_out, header, "Basic %s", base64_encode(orig_request-&gt;peer_login)); </code></pre> <p>I haven't found any proxy servers that can pass a request along to another proxy with digest authentication enabled; if you can find one that supports digest auth for an upstream proxy, I'd recommend using that.</p> <p>Otherwise, I'd recommend using a different protocol than HTTP; use <code>ssh:</code> if you need authentication, or the raw <code>git:</code> protocol if you're just pulling changes down from a public server.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

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