You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Becker, Thomas" <Th...@torex.com> on 2011/07/26 10:34:49 UTC
1.7 compatibility issue
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://xxxx:8443/yyyy
svn: E175009: Unable to connect to a repository at URL
'https://xxxx:8443/yyyy'
svn: E175009: XML parsing failed: (400 Bad Request)
The Visual SVN event log shows the message "Hostname xxxx:8443 provided
via SNI and hostname xxxx provided via HTTP are different". There seems
to be a missing port number which reminded me of a discussion in thread
"1.7.0-alpha1 feedback"
(http://svn.haxx.se/users/archive-2011-06/0263.shtml). Maybe this is
related.
Versions svn-1.7.0-dev-win32-r1136035.zip and earlier work, though.
Regards,
Thomas
This email and its attachments may be confidential and are intended solely for
the use of the individual to whom it is addressed. Any views or opinions expressed
are solely those of the author and do not necessarily represent those of Torex
(Torex Group of Companies). If you are not the intended recipient of this email
and its attachments, you must take no action based upon them, nor must you copy
or show them to anyone. Please contact the sender if you believe you have received
this email in error.
Torex Retail Solutions GmbH
Sitz der Gesellschaft: Berlin. HRB 102273B Amtsgericht Berlin Charlottenburg.
UST.-ID: DE170817515. Steuer-Nr. 27/448/07028. WEEE-Reg.-Nr. DE 30664749.
Geschaftsfuhrer: Stephen Callaghan, Martin Timmann.
.
Re: 1.7 compatibility issue
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Tue, Jul 26, 2011 at 20:45, Ivan Zhakov <iv...@visualsvn.com> wrote:
> On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov <iv...@visualsvn.com> wrote:
>> On Tue, Jul 26, 2011 at 13:37, Becker, Thomas <Th...@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
>
Fixed in r1151177 and nominated for backport to 1.7.x.
Thanks for bug report!
--
Ivan Zhakov
Re: 1.7 compatibility issue
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov <iv...@visualsvn.com> wrote:
> On Tue, Jul 26, 2011 at 13:37, Becker, Thomas <Th...@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
Re: 1.7 compatibility issue
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Tue, Jul 26, 2011 at 13:37, Becker, Thomas <Th...@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
--
Ivan Zhakov
AW: 1.7 compatibility issue
Posted by "Becker, Thomas" <Th...@torex.com>.
Yes, yyyy actually starts with svn. The URL looks like this: https://<server>:8443/svn/<repository_name>
Regards,
Thomas
-----Ursprüngliche Nachricht-----
Von: Ivan Zhakov [mailto:ivan@visualsvn.com]
Gesendet: Dienstag, 26. Juli 2011 11:26
An: Becker, Thomas
Cc: users@subversion.apache.org
Betreff: Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 12:34, Becker, Thomas <Th...@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://xxxx:8443/yyyy
>
> svn: E175009: Unable to connect to a repository at URL
> 'https://xxxx:8443/yyyy'
>
The URL for VisualSVN Server repositories should be like
https:/xxx:8443/svn/yyyy. Please make sure that you are using correct
URL to repository.
--
Ivan Zhakov
This email and its attachments may be confidential and are intended solely for
the use of the individual to whom it is addressed. Any views or opinions expressed
are solely those of the author and do not necessarily represent those of Torex
(Torex Group of Companies). If you are not the intended recipient of this email
and its attachments, you must take no action based upon them, nor must you copy
or show them to anyone. Please contact the sender if you believe you have received
this email in error.
Torex Retail Solutions GmbH
Sitz der Gesellschaft: Berlin. HRB 102273B Amtsgericht Berlin Charlottenburg.
UST.-ID: DE170817515. Steuer-Nr. 27/448/07028. WEEE-Reg.-Nr. DE 30664749.
Geschäftsführer: Stephen Callaghan, Martin Timmann.
.
Re: 1.7 compatibility issue
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On Tue, Jul 26, 2011 at 12:34, Becker, Thomas <Th...@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://xxxx:8443/yyyy
>
> svn: E175009: Unable to connect to a repository at URL
> 'https://xxxx:8443/yyyy'
>
The URL for VisualSVN Server repositories should be like
https:/xxx:8443/svn/yyyy. Please make sure that you are using correct
URL to repository.
--
Ivan Zhakov
AW: 1.7 compatibility issue
Posted by "Becker, Thomas" <Th...@torex.com>.
I can confirm that listing the repository works with --config-option
servers:global:http-library=neon.
As reported by Ivan he fixed this issue in r1151177.
Thanks!
Regards,
Thomas
________________________________
Von: Mark Phippard [mailto:markphip@gmail.com]
Gesendet: Dienstag, 26. Juli 2011 18:17
An: Becker, Thomas
Cc: users@subversion.apache.org
Betreff: Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 11:44 AM, Becker, Thomas
<Th...@torex.com> wrote:
Sorry for the confusion: yyyy stands for svn/<repo_name>, xxxx
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/
This email and its attachments may be confidential and are intended solely for
the use of the individual to whom it is addressed. Any views or opinions expressed
are solely those of the author and do not necessarily represent those of Torex
(Torex Group of Companies). If you are not the intended recipient of this email
and its attachments, you must take no action based upon them, nor must you copy
or show them to anyone. Please contact the sender if you believe you have received
this email in error.
Torex Retail Solutions GmbH
Sitz der Gesellschaft: Berlin. HRB 102273B Amtsgericht Berlin Charlottenburg.
UST.-ID: DE170817515. Steuer-Nr. 27/448/07028. WEEE-Reg.-Nr. DE 30664749.
Geschaftsfuhrer: Stephen Callaghan, Martin Timmann.
.
Re: 1.7 compatibility issue
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Jul 26, 2011 at 11:44 AM, Becker, Thomas <Th...@torex.com>wrote:
> Sorry for the confusion: yyyy stands for svn/<repo_name>, xxxx 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/
AW: 1.7 compatibility issue
Posted by "Becker, Thomas" <Th...@torex.com>.
Sorry for the confusion: yyyy stands for svn/<repo_name>, xxxx stands
for <server_host>. The URL looks like
https://<server_host>:8443/svn/<repo_name>.
Regards,
Thomas
________________________________
Von: Mark Phippard [mailto:markphip@gmail.com]
Gesendet: Dienstag, 26. Juli 2011 16:54
An: Becker, Thomas
Cc: users@subversion.apache.org
Betreff: Re: 1.7 compatibility issue
On Tue, Jul 26, 2011 at 4:34 AM, Becker, Thomas
<Th...@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://xxxx:8443/yyyy
svn: E175009: Unable to connect to a repository at URL
'https://xxxx:8443/yyyy'
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/
This email and its attachments may be confidential and are intended solely for
the use of the individual to whom it is addressed. Any views or opinions expressed
are solely those of the author and do not necessarily represent those of Torex
(Torex Group of Companies). If you are not the intended recipient of this email
and its attachments, you must take no action based upon them, nor must you copy
or show them to anyone. Please contact the sender if you believe you have received
this email in error.
Torex Retail Solutions GmbH
Sitz der Gesellschaft: Berlin. HRB 102273B Amtsgericht Berlin Charlottenburg.
UST.-ID: DE170817515. Steuer-Nr. 27/448/07028. WEEE-Reg.-Nr. DE 30664749.
Geschaftsfuhrer: Stephen Callaghan, Martin Timmann.
.
Re: 1.7 compatibility issue
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Jul 26, 2011 at 4:34 AM, Becker, Thomas <Th...@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://xxxx:8443/yyyy****
>
> svn: E175009: Unable to connect to a repository at URL '
> https://xxxx:8443/yyyy'****
>
> 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/