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

Re: Authentication problem with clients > 1.7.22

From: Krzysztof Smiechowicz <deadwood_at_wp.pl>
Date: Thu, 28 Jul 2016 17:34:36 +0200

W dniu 28.07.2016 o 10:01, Stefan Sperling pisze:
> On Wed, Jul 27, 2016 at 06:56:46PM +0200, Krzysztof Smiechowicz wrote:
>> Hi All,
>>
>> We are having problems accessing our svn server via https with client newer
>> than 1.7.22 - 1.8.16 and 1.9.3 to be specific. The problem is that the newer
>> clients come up with authentication request during svn checkout which after
>> entering correct password fails. The authentication comes at random moments
>> during checkout. The difference we could spot so far was that 1.7.22 was
>> using ra_neon and newer clients are using ra_serf for HTTPS.
>
> My guess is that you need to increase the MaxKeepAliveRequests setting
> in httpd.conf on the SVN server.
>
> Once the MaxKeepAliveRequests limit is reached the server closes the
> connection so the client opens a new one and authenticates again.
>
> Serf-based clients send a lot more requests than Neon-based clients.
> It seems the Neon-based clients do not trigger the limit in your
> situations, while Serf-based clients do.
>

Hello,

Thank you for reply. We set this setting to 0 (unlimited), but the problem persists. Should this be entered into
Subversion bugtracker?

Best regards,
Krzysztof
Received on 2016-07-28 17:34:55 CEST

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.