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

RE: [TSVN and svn 1.8.0] Cannot Digest Authenticate.

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 3 Jul 2013 09:04:39 +0200

> -----Original Message-----
> From: Camilo S. Tsumanuma [mailto:veriwell_at_veriwell.com.br]
> Sent: vrijdag 21 juni 2013 16:22
> To: users_at_subversion.apache.org
> Subject: [TSVN and svn 1.8.0] Cannot Digest Authenticate.
>
> Hi Dear Subversion Users Forum,
>
> I compiled subversion 1.8.0 in CentOS 6.4 using
> http://comments.gman%e2%80%8be.org/gmane.comp.ver%e2%80%8bsion-control.subvers%e2%80%8b
> ion.user/113594
> as guideline.
>
> I just used my own previous Apache Server configuration of
> Digest Authentication for WebDav SVN but it failed
> like described in Discussion Topic of TortoiseSVN Users Forum
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess
> ageId=3058687.

What setting does your apache use for KeepAlive?

Currently serf doesn't support digest authentication with KeepAlive off (which will be fixed with Serf 1.3.0, which should be available before Subversion 1.8.1)

Subversion performs much better to servers with keep alive enabled and the difference will be even better if you allow a huge number of requests on one connection. (The Subversion 1.7 release notes recommend a maximum setting of at least 1000)

Without keep alives a new http or https connection has to be setup for every request, while with keep alives a single connection can not only handle multiple requests after another, but also multiple requests at the same time.

        Bert
Received on 2013-07-03 09:05:45 CEST

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