Thanks for the reply. The user claims that they aren't doing that
(changing the username halfway through the commit), at least not
intentionally or to their knowledge. Now they are reporting that it
works sometimes, but not others. Is this a potential Svn configuration
issue at our site? On the client PC perhaps?
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Thursday, August 04, 2005 3:26 PM
To: dkrobbins
Cc: users@subversion.tigris.org
Subject: Re: Error on Commit (501 Method Not Implemented)
On Aug 4, 2005, at 9:45 AM, dkrobbins@micron.com wrote:
> I have a user that had been able to commit files into Subversion until
> just recently. Now he cannot commit files to any repository. The error
> he gets back from Svn is "501 Method Not Implemented". If I go look at
> the Apache error log, I see the following entries for his failure:
>
> [Wed Aug 03 17:24:09 2005] [error] Access denied: 'migmate_sv'
> CHECKOUT
> Scripts:/trunk/MigMateUpdate.pl
> [Wed Aug 03 17:24:14 2005] [error] Could not fetch resource
> information.
> [501, #0]
> [Wed Aug 03 17:24:14 2005] [error] Multi-author commits not supported.
> [501, #0]
>
> In case it is important, we use LDAP for authentication.
>
> Any ideas?
Yeah, this error means that the client changed authentication halfway
through the commit. That is, it started the commit by sending http
requests with a Basic auth header of user1, and then a few requests
later it sent a Basic auth header with a different user.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 5 21:13:56 2005