Andy Levy wrote on Tue, Apr 26, 2011 at 13:58:08 -0400: > On Tue, Apr 26, 2011 at 06:47, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > > Andy Levy wrote on Tue, Apr 26, 2011 at 06:26:47 -0400: > >> On Fri, Apr 22, 2011 at 11:04, Daniel Shahaf <d...@daniel.shahaf.name> > >> wrote: > >> > Andy Levy wrote on Fri, Apr 22, 2011 at 10:56:14 -0400: > >> >> But our authz file is written as [Code:/path] and when committing, we > >> >> get 403 Forbidden errors because no rules match - the user is > >> >> committing to code and the rule checks for Code, case-sensitive. > >> >> > >> >> It's an easy enough fix on the client side, but it is an annoyance. > >> > > >> > I'm willing to accept that as a bug report, by the way. The > >> > before-the-colon section is defined as 'the basename of the repository > >> > directory', so it seems logical to me that it would be case-sensitive if > >> > the repository is on a case-insensitive filesystem (regardless of OS). > >> > >> I've read this a half-dozen times and I'm still missing something, I'm > >> just not understanding it. > >> > > > > Consider this setup: > > > > % svnadmin create /path/to/foo > > % svn mkdir -mm file:///path/to/foo/bar > > % svn mkdir -mm file:///path/to/foo/BAR > > % cat <<EOF > /path/to/authz-file > > [FOO:/bar] > > * = r > > root = rw > > EOF > > % > > > > On a case-sensitive filesystem, the [FOO:/bar] clause refers to > > a repository called 'FOO', which, in general, is not the same as 'foo'. > > > > On a case-insensitive filesystem, ./foo and ./FOO refer to the same > > object, therefore --- I argued --- it makes sense to respect both > > [foo:/bar] and [FOO:/bar] entries in the authz file when a request to > > a repository named *either* 'foo' or 'FOO' is seen. > > > > The paths within the repository (such as '/bar') are always case-sensitive. > > > > (Using terminology from trunk's svn_dirent_uri.h, in the authz file > > entry [FOO:/bar], 'FOO' is a dirent and 'bar' is an fspath.) > > > > Is that clearer? > > Much clearer, thanks. > > Do you want me to go ahead and write this up as a bug & submit to the > tracker? Or wait till I can test w/ svnserve and/or a newer SVN > release
If you'd like to file the bug now, you have my +1, just please state in the bug what version you reproduced it with. (Thanks!) > (I'm guessing the current release has the same affliction, > from your responses)? I don't know what releases the bug may be in --- I use a case-insensitive filesystem.
