Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Authentication problem with clients > 1.7.22
To: users@subversion.apache.org
References: <2a3e5af7-9649-025e-154d-216ec27de94c@wp.pl>
 <20160728080152.GA10889@byrne.stsp.name>
From: Krzysztof Smiechowicz <deadwood@wp.pl>
Message-ID: <7fa7eec4-cf83-d52a-6d48-79b1b456dbe3@wp.pl>
Date: Thu, 28 Jul 2016 17:34:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160728080152.GA10889@byrne.stsp.name>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Thu, 28 Jul 2016 15:34:55 -0000

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