subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohsin Abbas <mohsinchan...@gmail.com>
Subject Re: Subversion 1.8.9 repository access issue [Urgent]
Date Wed, 21 May 2014 00:14:25 GMT
Hello Sir,

403 permission denied issue has been resolved after removing trailing
slash. Thanks for help.

Now one more issue i am facing when i access repositories URL in Tortoise
SVN client it gives unable to parse error [207 response code used with
WEBDAV protocol]. But old svn 1.4.2 repositories are accessible with same
Tortoise SVN but when I import 1.4.2 repositories in new svn 1.8.9
following error occurred.

FYI
SVN Client :
TortoiseSVN 1.6.7

When I hit the URL in browser all data display correctly but in tortoise
svn client 207 displays.

In Apache error log:

x.x.x.x - mabbas [21/May/2014:00:52:02 -0400] "PROPFIND
/svn/x/x/!svn/vcc/default HTTP/1.1" *207* 467
x.x.x.x - mabbas [21/May/2014:00:52:02 -0400] "PROPFIND
/svn/x/Ix/!svn/bc/24446/Trunk/Source/JavaAGI/docs HTTP/1.1" *207 *449
x.x.x.x - mabbas [21/May/2014:00:52:02 -0400] "PROPFIND
/svn/x/x/!svn/bc/24446/Trunk/Source/JavaAGI/docs HTTP/1.1" *207 *3858



On Tue, May 20, 2014 at 11:34 AM, Stefan Sperling <stsp@elego.de> wrote:

> On Tue, May 20, 2014 at 03:13:45PM +0500, Mohsin Abbas wrote:
> > Sir ,
> >
> > Thanks for your quick response.
> > Here i want to ask question in my previous server with subversion 1.4.2
> > this trailing slash works fine as i had already mentioned in my first
> email
> > i copied same configurations which are working absolutely fine with
> > subversion 1.4.2 why this is not working with subversion 1.8.9 either
> this
> > is some limitations in new svn version ? or some other issue ?
> >
> > Regards
>
> I don't know exactly why this was changed.
> It's possible that this change in behaviour was intentional.
>
> It might have been this change: http://svn.apache.org/r1037662
> The tests added there treats the path "/a/" as invalid, so your the path
> "Devices:/Trunk/" you use in the authz file is now also invalid.
>

Mime
View raw message