Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 12:34, Becker, Thomas thomas.bec...@torex.com wrote: Hi, I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from Collabnet (https://ctf.open.collab.net/sf/frs/do/viewRelease/projects.csvn/frs.svn_binaries.windows ). With the “alpha” and “beta” clients I get the following error: svn.exe ls https://:8443/ svn: E175009: Unable to connect to a repository at URL 'https://:8443/' The URL for VisualSVN Server repositories should be like https:/xxx:8443/svn/. Please make sure that you are using correct URL to repository. -- Ivan Zhakov
Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 4:34 AM, Becker, Thomas thomas.bec...@torex.comwrote: Hi, ** ** I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from Collabnet ( https://ctf.open.collab.net/sf/frs/do/viewRelease/projects.csvn/frs.svn_binaries.windows). ** ** With the “alpha” and “beta” clients I get the following error: ** ** svn.exe ls https://:8443/ svn: E175009: Unable to connect to a repository at URL ' https://:8443/' svn: E175009: XML parsing failed: (400 Bad Request) Does the SVN ls command even support this? I was not aware that it did. When I try it from OSX using 1.6 and 1.7 this is what I get: 1.6: $ /usr/bin/svn ls http://cu171.cloud.sp.collab.net/svn/ svn: Repository moved temporarily to 'http://cu171.cloud.sp.collab.net/svn/'; please relocate 1.7: $ svn ls http://cu171.cloud.sp.collab.net/svn/ svn: E175011: Unable to connect to a repository at URL ' http://cu171.cloud.sp.collab.net/svn' subversion/libsvn_ra_neon/util.c:607: (apr_err=175011) svn: E175011: Repository moved temporarily to ' http://cu171.cloud.sp.collab.net/svn'; please relocate In my case the server is running 1.7 as well. I can browse the list of repositories using my web browser. FWIW, that is all I thought this feature was supposed to support. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 11:44 AM, Becker, Thomas thomas.bec...@torex.comwrote: Sorry for the confusion: stands for svn/repo_name, stands for server_host. The URL looks like https:// server_host:8443/svn/repo_name. So you are saying you cannot even do svn ls against a repository? The automated test suite would exercise that. It could be some incompatibility between the client binaries and the way VisualSVN configures authentication or something like that. The binaries are probably using ra_serf to talk to the repository, which is new in 1.7. You can try configuring your client to use Neon as the default. Edit %APPDATA%\Subversion\config and add: http-library = neon At the bottom. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 13:37, Becker, Thomas thomas.bec...@torex.com wrote: Yes, 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 :8443 -- Ivan Zhakov
Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov i...@visualsvn.com wrote: On Tue, Jul 26, 2011 at 13:37, Becker, Thomas thomas.bec...@torex.com wrote: Yes, 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 :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
Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 20:45, Ivan Zhakov i...@visualsvn.com wrote: On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov i...@visualsvn.com wrote: On Tue, Jul 26, 2011 at 13:37, Becker, Thomas thomas.bec...@torex.com wrote: Yes, 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 :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 Fixed in r1151177 and nominated for backport to 1.7.x. Thanks for bug report! -- Ivan Zhakov
