Note that there are some explanatory texts on larger screens.

plurals
  1. POUnknown protocol error when using git-svn over HTTPS through a proxy server
    primarykey
    data
    text
    <p>I've been encountering some problems attempting to access a Subversion repository via HTTPS using git-svn.</p> <p>When I type <code>git svn init --username=&lt;my username&gt; --trunk=https://&lt;host&gt;/&lt;project&gt;/trunk</code>, I get the following error message:</p> <pre><code>RA layer request failed: PROPFIND request failed on '/&lt;project&gt;/trunk': PROPFIND of '/&lt;project&gt;/trunk': SSL negotiation failed: SSL error: unknown protocol (https://&lt;host&gt;) at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 2299 </code></pre> <p>A couple of other points to note:</p> <ol> <li>I'm using msysgit 1.7.9.0 on Windows 7 x64. I also have the Subversion 1.7.1 command line client and TortoiseSVN 1.7.1 installed.</li> <li>I am connecting through a proxy server, which I have specified through both the HTTP_PROXY environment variable and <code>git config http.proxy</code>.</li> <li>I am able to clone Github repositories over HTTPS on the same machine without problems.</li> <li>The plain Subversion client checks out the same project without problems. I have also been able to clone it successfully with Mercurial and hgsubversion, although it did fail to recognise the server's SSL certificate, so I had to specify it explicitly in my mercurial.ini file. Because of this, I am using <code>git config http.sslVerify=false</code>. However, this does not make any difference.</li> <li>One-way workarounds such as using svnsync (as e.g. suggested <a href="https://stackoverflow.com/questions/4838834/svn-to-git-import-problem-using-git-svn-clone">here</a>) are not an option.</li> </ol> <p>Anything else that I haven't tried?</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.
 

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