[SVN-3709] Inconsistency between "svn list" and "svn checkout"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.x
• Fix Version/s: 1.6.15
• Component/s: cmdline client
• Assignee: C. Michael Pilato
• Reporter: Subversion Importer
• Created: 14/Sep/10 07:38
• Updated: 27/Oct/18 16:29
• Resolved: 29/Mar/11 21:53

Description

According to the documentation, the "svn list" command should "list each TARGET
file and the contents of each TARGET directory as they exist in the repository."
This does not seem to be true for repositories with path-based authorization.

In contrast to checkout operations, which skip subfolders of a given repository
that the respective user does not have access to, the list command breaks on the
first inaccessible subdiretory.

This can be reproduced with the following simple command (thanks to Daniel
Shahaf for confirming):

  $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

In contrast, a checkout operation on the same repository will successfully
retrieve all the files an anonymous user has access to, skipping the "private"
folder:

  $svn co http://svncorp.org/svncorp/svn/trunk
  ...
  Checked out revision 284.

I suggest to let the list command continue even if a certain subfolder is
inaccessible. See also the discussion at
<http://svn.haxx.se/users/archive-2010-09/0257.shtml>.

http://svn.haxx.se/users/archive-2010-09/0257.shtml

Original issue reported by sidewinder

Issue Links

• blocks: SVN-3504 Hide restricted directories when using path-based authorization
• is depended upon by: SVN-3504 Hide restricted directories when using path-based authorization