Bug report: Issue #146 not completely resolved.
From: Jerry Qassar <Jerry.Qassar_at_kratosdefense.com>
Date: Thu, 8 Nov 2012 19:58:57 +0000
describes an issue where the repository browser of TortoiseSVN doesn't show directories when a user has no access to a parent directory but does have access to a child. A fix was provided that adds the exact path manually.
Unfortunately, this fix does not seem to work in all instances. We have a use case where a user is still forbidden to browse items in a subdirectory of a directory to which he has access. The setup looks like this:
+ - Root level (no access)
o - subdir1...n (no access)
o - userdir (has r/w access)
o - branches (empty)
o - docs (not empty)
o - releases (empty)
o - trunk (empty)
The relevant section of the auth file looks like this:
The user reports that when viewing the repository via web browser, he is able to view all directories under userdir, whether they are empty or not. However, in Tortoise, when trying to browse empty subdirectories, they receive a 403 error. The non-empty docs directory is browseable. The exception is (possibly) when your very first directory browsed to is one of the empty directories. Once you switch to a different directory you are forbidden at the first child level to which you do not have access (the root, in this case).
It seems that the fix in place right now is not properly constructing paths for target directories that do not themselves have children or contents. This can be worked around by having an admin place dummy files, but this is not ideal. Some help with a fix would be greatly appreciated.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
This is an archived mail posted to the TortoiseSVN Users mailing list.