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

Re: SSPI reauthentication during commit fails it

From: Eric Lemes <ericlemes_at_gmail.com>
Date: 2007-03-29 14:59:50 CEST

On 3/29/07, techtonik <techtonik@gmail.com> wrote:
> Hello,
> Yet another problem with Subversion and NTLM / SSPI.
> During commit after successful authentcation at the beginning and a
> couple of requests afteerward server sends second request to
> reauthenticate and at that point commit fails. In my case request for
> reauthentication is sent after approximately 230 files 1.1Mb in total,
> but it is possible to force reauthentication on every request with
> "SSPIPerRequestAuth On" and then commit fails almost immediately.
> I've tried to connect over HTTPS with standard SVN 1.4.3 binary and
> with one compiled against Neon 0.25.5 and the result is the same. I
> attach log of HTTPS request with "SSPIPerRequestAuth On" using
> standard SVN 1.4.3 client binary for windows.


I have a similar problem, in a Windows 2003 SVN Server (1.4.0 Apache 2.0.x).

If the repos has a name REPOS in the server, and you checkout it as
http://server/svn/repos, the authorization works in the checkout/update but
fails in commit.

You need to relocate the working copy to http://server/svn/REPOS (I can do
this in TortoiseSVN). Then the commit works.

Received on Thu Mar 29 15:00:20 2007

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.