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 14:22:48 GMT
Hello sir,

I have installed Apache 2.2.27 with subversion 1.8.9  version you are
saying this Apache version is venerable for this issue ? right ? Now please
tell me what Apache version should I use which is not venerable for this
issue ?

Regards



On Wed, May 21, 2014 at 2:21 PM, Stefan Sperling <stsp@elego.de> wrote:

> On Wed, May 21, 2014 at 12:14:25AM +0000, Mohsin Abbas wrote:
> > 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
>
> It sounds like you're running into httpd issue 56480:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=56480
> Note: This is a bug in Apache HTTPD, not Apache Subversion.
>
> Downgrading to httpd 2.2.24 or 2.4.4 should work around it
> until a fix is available. This is a bit tricky because such
> a downgrade would also undo some security fixes.
>
> If you compile your own HTTPD then applying the patch which
> can be found in issue 56480 would be the best thing to do.
>
> As explained in issue 56480 the problem has some history but
> intially started with this change:
>
>   *) mod_dav: Ensure URI is correctly uriencoded on return. PR 54611
>      [Timothy Wood <tjw omnigroup.com>]
> See http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/CHANGES
> or  http://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES
>

Mime
View raw message