pre-lock hooks running when repository accessed via web browser

Hi,

There was no response to the post below in users list, so I am posting to
dev list.

1) Is there any way to prevent the pre-lock hooks from firing when someone
opens a word doc in a SVN URL via a standard web browser? (note: post-lock
never fires in this case)

2) Is there any way for the pre-lock hook to know if the hook is being fired
do to a SVN client requesting a lock versus it being fired because a user
opening a word doc SVN URL via a web browser?

This is pre-lock fire from web browser access is causing issues with the
notification emails we have setup.

Thanks,

Mark

---------- Forwarded message ----------
From: Mark <email2mark_at_gmail.com>
Date: Mon, Jun 30, 2008 at 2:46 PM
Subject: pre-lock hooks running when repository accessed via web browser
To: users_at_subversion.tigris.org

We have pre-lock and post-lock hooks setup. The pre-lock hook denies users
access to create locks certain areas of the repository. Users can't commit
in those areas via the pre-commit hook (even though they have write access
via the authz file) so we though it best to prevent them for locking and
editing there as well.

What we have found is that when users access these restricted areas in the
repository with a web browser via a direct svn URL to a specific file, the
pre-lock hooks are run. When this occurs, the hooks send out a email to
notify that the pre-lock hook failed because the user is not allowed to lock
those areas of the repo. The user is able to view/save the file via the web
browser.

- apache 2.2.8
- openssl 0.9.8h
- svn 1.4.6

Any reason why accessing a file in a subversion repo via a web browser is
causing the pre-lock hooks to run?

Are there any other hooks that are run when a subversion repo is accesses in
this way?

Thanks
Received on 2008-09-22 15:20:19 CEST