> [Tue Feb 05 19:53:05.667189 2013] [ssl:debug] [pid 32165:tid 139847839336192] > ssl_engine_kernel.c(1886): [client 217.158.253.219:35439] AH02041: Protocol: > TLSv1, Cipher: RC4-SHA (128/128 bits) > [Tue Feb 05 19:53:05.673932 2013] [ssl:error] [pid 32165:tid 139847839336192] > AH02033: No hostname was provided via SNI for a name based virtual host > > (This is an httpd v2.4.3 SSL host with SSLStrictSNIVHostCheck set to on) > > I was using svnkit-1.7.9-SNAPSHOT_r9555_v20130205_1914. Did you run client with JVM 1.7?
Alexander Kitaev, TMate Software, http://subgit.com/ - Svn to Git Migration! http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 5 February 2013 20:56, Graham Leggett <minf...@sharp.fm> wrote: > On 05 Feb 2013, at 9:30 PM, Alexander Kitaev <kit...@gmail.com> wrote: > >> I've made changes in SVNKit to make it support SNI "out of the box". >> The most recent version of SVNKit now sends correct request to the >> https://sni.velox.ch/ >> You may get new SVNKit binaries with these changes at >> http://teamcity.tmatesoft.com/viewLog.html?buildId=5276&tab=artifacts&buildTypeId=bt43 >> >> If possible, could you please try running checkout with that new >> version to see if it still hangs on connect? > > The hang on connect is gone, and jsvn picks up the client certificate and > uses it correctly. > > No joy with SNI though, I get this in the server log: > > [Tue Feb 05 19:53:05.667189 2013] [ssl:debug] [pid 32165:tid 139847839336192] > ssl_engine_kernel.c(1886): [client 217.158.253.219:35439] AH02041: Protocol: > TLSv1, Cipher: RC4-SHA (128/128 bits) > [Tue Feb 05 19:53:05.673932 2013] [ssl:error] [pid 32165:tid 139847839336192] > AH02033: No hostname was provided via SNI for a name based virtual host > > (This is an httpd v2.4.3 SSL host with SSLStrictSNIVHostCheck set to on) > > I was using svnkit-1.7.9-SNAPSHOT_r9555_v20130205_1914. > > Regards, > Graham > -- >
