Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C77B11AE4 for ; Wed, 21 May 2014 00:14:52 +0000 (UTC) Received: (qmail 39526 invoked by uid 500); 21 May 2014 00:14:52 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 39494 invoked by uid 500); 21 May 2014 00:14:52 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 39487 invoked by uid 99); 21 May 2014 00:14:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 May 2014 00:14:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mohsinchandia@gmail.com designates 209.85.128.179 as permitted sender) Received: from [209.85.128.179] (HELO mail-ve0-f179.google.com) (209.85.128.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 May 2014 00:14:48 +0000 Received: by mail-ve0-f179.google.com with SMTP id oy12so1577411veb.38 for ; Tue, 20 May 2014 17:14:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0xUBMm+6xCmHDOVe9PIM6LpmahSfzG4DMl9d+3oPOgw=; b=EWLhPgK0p4H45/VWnoR/ssvveV9qHeik4ykl3eUi30n9ttDWitBBRkxFc16WqNPYWT wllYD/Va9hRA9HchgwfmYg5WaduWiTp2SfreB6f22kHojHie6GCIIrmM5jTjRkC4D+dZ Bpj+GdPvWbqJ/VYavXHt9KZqWtil79kcvLkXWNvZp4EZK65thC4U170MhyFwX83QyXky pFhkwqIqwPATfQUC9DqOYI/PirCNTyuVUnyKem7mQQ0uA48aHs65TZMr4zwa+RERPGap TKyI7yBxujwNkA5ysYaMX78hQMHEFXGaARf2keCmhzFcdaIxiMhZlUrQBhEno85x0JQY t3EQ== MIME-Version: 1.0 X-Received: by 10.221.40.193 with SMTP id tr1mr6701813vcb.31.1400631265105; Tue, 20 May 2014 17:14:25 -0700 (PDT) Received: by 10.220.92.202 with HTTP; Tue, 20 May 2014 17:14:25 -0700 (PDT) In-Reply-To: <20140520113445.GC20473@ted.stsp.name> References: <20140520091610.GA11975@ted.stsp.name> <20140520113445.GC20473@ted.stsp.name> Date: Wed, 21 May 2014 00:14:25 +0000 Message-ID: Subject: Re: Subversion 1.8.9 repository access issue [Urgent] From: Mohsin Abbas To: Mohsin Abbas , users@subversion.apache.org, julianfoad@apache.org Content-Type: multipart/alternative; boundary=001a11336a8e049dcf04f9dde123 X-Virus-Checked: Checked by ClamAV on apache.org --001a11336a8e049dcf04f9dde123 Content-Type: text/plain; charset=UTF-8 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 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. > --001a11336a8e049dcf04f9dde123 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Sir,

403 permission deni= ed issue has been resolved after removing trailing slash. Thanks for help.<= br>
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/2= 014:00:52:02 -0400] "PROPFIND /svn/x/Ix/!svn/bc/24446/Trunk/Source/Jav= aAGI/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, M= ay 20, 2014 at 11:34 AM, Stefan Sperling <stsp@elego.de> wrote:<= br>
On T= ue, 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 t= he path
"Devices:/Trunk/" you use in the authz file is now also invalid.<= br>

--001a11336a8e049dcf04f9dde123--