Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v746.2)
In-Reply-To: <43F0C870.4000509@web.turner.com>
References: <43EFA041.3040705@apache.org>
 <B7D8CD5D-7F87-47F0-BCCE-E7C8466F3341@jaguNET.com>
 <4CBC96DB-2C07-4F6F-8C43-B9708ED95584@jaguNET.com>
 <43F0C870.4000509@web.turner.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C8F40475-7E9D-4012-9B5E-5B836C3E2C0B@jaguNET.com>
Content-Transfer-Encoding: 7bit
From: Jim Jagielski <jim@jaguNET.com>
Subject: Re: [Patch] Keep Alive not workwing with mod_proxy  (PR38602)
Date: Mon, 13 Feb 2006 13:22:16 -0500
To: dev@httpd.apache.org


On Feb 13, 2006, at 12:57 PM, Brian Akins wrote:

> Jim Jagielski wrote:
>
>>  there is no guarantee that the next
>> kept-alive connection will go to the same backend;
>> as such, keeping it open is wasteful and re-using
>> it is downright wrong.
>
> Why?  Why would we care which backend a request goes to, in  
> general. And, do we not want to use keepalives as much as possible  
> to the backends?
>

Let's assume that you have Apache setup as a proxy and furthermore
it's configured so that /html goes to foo1 and /images goes
to /foo2.

A request comes in for /html/index.htm, and gets proxied to
foo1, as it should; the connection is kept-alive, and a
request for /images/blarf.gif is requested; this should not
be sent to the just kept-alive server, but instead to
foo2...

So we need to ensure that this doesn't happen. We had a similar
type bug when picking workers out, which was patched in
349723...