[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.7 compatibility issue

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Tue, 26 Jul 2011 20:45:44 +0400

On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On Tue, Jul 26, 2011 at 13:37, Becker, Thomas <Thomas.Becker_at_torex.com> wrote:
>> Yes, yyyy actually starts with svn. The URL looks like this: https://<server>:8443/svn/<repository_name>
>> Regards,
>>  Thomas
> Could you please try to add explicit ServerName configuration
> directive to "%VISUALSVN_SERVER%\conf\httpd-custom.conf" file and
> restart the server:
> ServerName xxxx:8443
I was able to reproduce the issue in my environment. It seems to be
bug in ra_serf/serf code: it sets SNI hostname to 'hostname:port',
while valid value is 'hostname' (without port).

So currently there're two workaround possible:
1. Use neon as http-library on client
2. Use default HTTPS port (443) on server

Ivan Zhakov
Received on 2011-07-26 18:46:45 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.