Re: User problem

Ben Collins-Sussman <sussman@collab.net> writes:

> 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.

I added the LimitExcept in the config but it didn't help with anything. All
commits are still done as 'anonymous'. I also checked the network traffic with
ethereal and Apache DID issue an auth challenge. The reply from the client also
included the auth key.

What's wrong?

-- 
- Jan Borsodi <jb_at_ez.no> - Systems Engineer @ eZ systems - Web: http://ez.no
  QtVu: http://www.qtvu.org  -  RegExplorer: http://regexplorer.sourceforge.net
  EMacro: http://emacro.sourceforge.net  -  Apollo: http://www.apolloplayer.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org