Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of JT.Miller@l-3com.com
 designates 166.20.51.112 as permitted sender)
From: JT.Miller@L-3com.com
To: Philip Martin <philip.martin@wandisco.com>
CC: "users@subversion.apache.org" <users@subversion.apache.org>
Subject: RE: Authentication Questions
Thread-Topic: Authentication Questions
Thread-Index: AdAp+UZWiaHTIYxXTC2YJSCoAs3ooABXNn0aAAAU2LA=
Date: Thu, 8 Jan 2015 15:50:31 +0000
Message-ID: 
 <EFF0047A9D3D2846843A594DA21A99FB09799E74@PLNEXCH01.mtg.l-3com.com>
References: 
 <EFF0047A9D3D2846843A594DA21A99FB09798D5D@PLNEXCH01.mtg.l-3com.com>
 <87egr5xpy9.fsf@ntlworld.com>
In-Reply-To: <87egr5xpy9.fsf@ntlworld.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks Philip, what you explained for the authz/authn caching makes sense. =
We recently performed a major upgrade of our IT infrastructure and I took t=
he opportunity to upgrade our very old Subversion configuration (old physic=
al server with Apache 2.2/SVN 1.4 to virtual server with 2.4/1.8). We have =
had some pretty significant latency issues (due to my ignorance of a proper=
 configuration). I was searching for performance bottlenecks and was (undul=
y) concerned by what I saw in the logs with debug enabled. Mostly I wanted =
to verify that the traffic pattern I showed was typical, and it doesn't sou=
nd like it's anything out of the ordinary.

I think the culprit for us was the default AcceptFilter directive. Changing=
 this to AcceptFilter http none seems to have cleared up all the latency is=
sues.

Thanks again for your explanation.

-----Original Message-----
From: Philip Martin [mailto:philip.martin@wandisco.com]=20
Sent: Thursday, January 08, 2015 9:17 AM
To: Miller, JT @ SSG - PE - MT
Cc: users@subversion.apache.org
Subject: Re: Authentication Questions

JT.Miller@L-3com.com writes:

> I guess there's no caching of credentials since the path-based=20
> authentication file can change at any time?

I'm not clear what you mean by "caching of credentials".  Subversion typica=
lly sends multiple HTTP requests over a single connection.  Each HTTP reque=
st has its own authn credentials and caching those would not make sense, al=
though Apache may cache any data used to validate the credentials.  Subvers=
ion's authz file is parsed when first needed and cached for use by any subs=
equent HTTP requests on the same connection.

--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*