(I'm not subscribed to the list, please keep me in CC)
I have an FSFS repository, accessible only through apache with
mod_dav_svn. I have to use strict access controls (even for reads), so I
Sometimes between upgrading from 1.4 to 1.5 the users have started to
complain about occasional authentication errors, which could be solved
only by deleting and checkouting their local repository.
The problem manifests in the following error:
$ svn update
svn: Server sent unexpected return value (403 Forbidden) in response to
OPTIONS request for 'https://repo/svn'
repo/svn is the root of the repository, to which the user don't have any
If the user deletes the local copy and issues a new svn checkout,
everything works for sometime, but later the same error occurs again.
In the above example he wants to update repo/svn/docs/iplists, for which
he has rights.
The svnaccess file contains (a lot more, but these two are relevant here):
@svnadmin = rw
* = rw
The given user is not in the svnadmin group (the members of that group
of course don't see these kind of errors).
This problem occurs at different places too, where the scenario is the
same (/ has limited access, and the user has only access to a deeped
We couldn't notice such strange errors before the 1.4->1.5 switch (on
the server) as far as I can remember...
BTW, I remember that I've tried to change from neon to serf (but I don't
remember where, only on the server, or on one of our clients) in the
1.4-era, which resulted similar errors, so I've switched back to neon.
The apache config:
AuthName "SVN authentication"
Allow From all
AddHandler mod_python .py
OS: FreeBSD 7-STABLE
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-25 00:35:23 CET