[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Fwd: svn: Lock request failed: 401 Authorization Required]

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-06-26 17:21:27 CEST

On 6/26/06, Jeb <jeb.beasley@penske.com> wrote:
> We are using Apache authentication/authorization to limit access, not
> subversion.
> Up until we got into this lock issue, this kind of authorization scheme
> is working well. The problem surfaced when users set the needs-lock
> property on files.
> As I understand, the mod_authz_svn mechanism does not do any pattern
> matching, and out tests indicate that if we have a rule for
> [repo/project/branches/dev]
> that is does not match
> repo/project/branches/dev/module/source.ext
> We have branches like dev_gh, dev_phase2, dev_pl and based on the
> parent project control access to group members for that group.
> When I request a lock, the apache logs show several authenticated
> propfinds, and then a LOCK request without the authentication token.
> (Log snippet attached to previous message)


doesn't match /ecomm/.*/webprojects? I think there's one forward slash too many?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 26 17:23:41 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.