[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: techtonik <techtonik_at_gmail.com>
Date: 2007-04-06 14:37:06 CEST

On 4/6/07, Bert Huijben <bert-svn@qqn.nl> wrote:

> > -----Original Message-----
> > From: techtonik [mailto:techtonik@gmail.com]
> >
> > Tested with Neon 0.26.3 - the save problem - after 100 successful
> > requests server proposes to authenticate again and commit fails.
> >
> > Debug log is attached.
> The SSPI authentication works with keep-alive connections; after an initial successful authorization the connection stays authorized for multiple requests over the same connection. Apache by default limits the number of requests to 100 per connection. (The number you see)
> The default configuration of apache is
> MaxKeepAliveRequests 100
> (See http://httpd.apache.org/docs/2.2/mod/core.html#maxkeepaliverequests)
> So a workaround might be to set this number higher; but I think neon should transparently try to use a new connection without asking subversion to authenticate again.

When basic authorization is turned on there is no problem with Apache.
Subversion client is not asked to authenticate again.

--anatoly t.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 6 14:37:28 2007

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