Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: error (nike.apache.org: encountered temporary error during SPF
 processing of domain of jim@jagunet.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: KeepAliveTimeout per vhost for non-async MPMs
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: 
 <CALK=YjN4+Qtouqv4f7PELbTdJpL2S56Zq=mAKWu+7oxwU-CS2w@mail.gmail.com>
Date: Tue, 3 Mar 2015 13:29:09 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <B16AD610-8B87-4CC3-9658-C04431F2434D@jaguNET.com>
References: 
 <CAKQ1sVOH7C9sSNdWvqA66sOUvR54mGothhhDinHP_JR5zAca9w@mail.gmail.com>
 <CAKQ1sVO-dvsaiwmwYNn14ibFd_x3MSScoygXEu-njB=PJ1Hxwg@mail.gmail.com>
 <CALK=YjN4+Qtouqv4f7PELbTdJpL2S56Zq=mAKWu+7oxwU-CS2w@mail.gmail.com>
To: dev@httpd.apache.org

:)
> On Mar 3, 2015, at 12:59 PM, Eric Covener <covener@gmail.com> wrote:
> 
> On Tue, Mar 3, 2015 at 12:45 PM, Yann Ylavic <ylavic.dev@gmail.com> wrote:
>> OTOH it makes it clear that the keepalive timeout belongs to the
>> IP:port the request was received on, and not to the server for which
>> the latest request was handled on that IP:port.
> 
> 
> I think I documented the behavior, but just to get it on the books.
> What you say above is definitely the rationalization, but I think if
> we can remember the last servers keepalivetimeout (migration problems
> aside) I think it is better to use it.