On Tue, Dec 7, 2010 at 1:11 PM, Andy Levy <andy.l...@gmail.com> wrote:
> On Tue, Dec 7, 2010 at 11:59, Nick Stokes > <randomaccessitera...@gmail.com> wrote: > > Hi all, > > > > I am serving our repositories over https, using Apache 2.2, via > mod_dav_svn, > > also using mod_authz_svn for per directory access control. Most users > find > > the error messages cryptic (when there is a permission related error on > > checkout, commit, so on...) and I am wondering if there is a way to > > customize these messages? > > > > For example, current (default?) set up spits out the following: > > > > If checkout fails due to insufficient permissions: > > svn: Server sent unexpected return value (403 Forbidden) in response to > > OPTIONS request for 'https://my.cool.server/foo/trunk' > > > > If checkout fails due to spelling error in repository name: > > svn: Server sent unexpected return value (403 Forbidden) in response to > > OPTIONS request for 'https://my.cool.server/f00/trunk' > > I don't think Subversion can tell the difference here. If my AuthZ > file specifies that I have access to /f00/trunk/ and I ask for > /foo/trunk/, all that's really known is that I asked for a path which > I do not have permission to access. Do you propose that the server > scan for all possible "similar" repositories/paths in an attempt to > find a match? > > No. I did not propose that. The question was simple: Is there way to customize error messages from httpd server (akin to customizing logs in apache as in http://tinyurl.com/svn-apache-logs)? When users see "Server sent unexpected return value..." they assume there is something wrong with the server itself, despite the keyword "Forbidden" that follows. Besides, there is the redundant/misleading/irrelevant-for-client stuff there (OPTIONS, MKACTIVITY, respos ID). e.g. svnserve error messages are much better.
