[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Inconsistency between "svn list" and "svn checkout"

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 13 Sep 2010 23:46:05 +0200

Sidewinder_GER wrote on Mon, Sep 13, 2010 at 22:53:11 +0200:
> When an "unprivileged" user performs an "svn list" on the repository,
> the following happens:
>
> > svn list --verbose --recursive svn://server/repository
> 1 user Sep 13 22:35 ./
> 1 user Sep 13 22:35 1_public/
> 1 user 123 Sep 13 22:35 1_public/1.txt
> 1 user Sep 13 22:35 2_secret/
> svn: Authorization failed
>
> The process aborts at the first subdirectory that is not accessible by
> the respective user.
...
> I would expect "svn list" to work in very much the same way than "svn
> checkout", which means that it should continue to run and show me the
> contents of the "3_public" subdirectory.

I agree. Could you please file an appropriate issue in our tracker (if
there isn't one already)?

FWIW, an easy way to reproduce this is:

  $svn ls -R http://svncorp.org/svncorp/svn/trunk
  ..
  subversion/svn/list-cmd.c:289
  subversion/libsvn_client/list.c:272
  subversion/libsvn_client/list.c:107
  subversion/libsvn_client/list.c:73
  ...
  svn: access to '/svncorp/svn/trunk/private' forbidden

Which yields error SVN_ERR_RA_DAV_MALFORMED_DATA under ra_serf and error
SVN_ERR_RA_DAV_FORBIDDEN under ra_neon. (I haven't tested ra_local and
ra_svn.) Ideally, the fix for this issue will include making ra_serf
return the latter (more specific) error code.

Thanks!

Daniel
Received on 2010-09-13 23:50:35 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.