Stefan Sperling <s...@elego.de> writes: > How do we avoid ambiguity when handling requests to nested Locations? > How can a client access a folder /bar inside a repository at Location /svn > if another repository exists at a nested Location /svn/bar?
Yes, I was surprised too! If we assume that /svn and /svn/foo are directories that contain repositories then there can be no overlap: <Location /svn> ... SVNParentPath /svn </Location> <Location /svn/foo> ... SVNParentPath /svn/foo </Location> /svn/repo/<something> and /svn/foo/repo/<something> cannot overlap. The only way there could be a problem is if /svn/foo were itself a repository, but the admin can ensure that is not the case. -- Philip
