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

Re: User problem

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-09-04 18:15:20 CEST

Jan Borsodi <jb@ez.no> writes:

> Jan Borsodi <jb@ez.no> writes:
> > Ben Collins-Sussman <sussman@collab.net> writes:
> >
> > > If you do get prompted for a password, then we need a network trace of
> > > the commit. Use ethereal or something to capture the http dialogue,
> > > and post it here.
> Here's the log, I checked out a simple directory (password required) and used
> the -N option to keep the HTTP traffic low. I then added a directory and
> committed (no password required).
Did you see the last mail from someone else on the list? It was a
good catch; you're using Limit instead of LimitExcept.

In other words, you've got the reverse behavior you want. You're
requiring a password on read operations, but not write operations.
That's why a password was required to checkout (when it shouldn't be),
and when you committed, Apache never bothered to issue an auth
challenge at all.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 4 18:17:13 2002

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

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