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)
From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <200610121411.k9CEBMN01070@devsys.jaguNET.com>
Subject: Re: Issue with persistent http proxy backend connection
To: dev@httpd.apache.org
Date: Thu, 12 Oct 2006 10:11:18 -0400 (EDT)
Reply-To: jim@jaguNET.com
In-Reply-To: <no.id> from "Ruediger Pluem" at Oct 12, 2006 01:19:51 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ruediger Pluem wrote:
> 
> I do not think that this matters all too much, because the backend closes
> the connection *immediately* after sending out the response. So the socket
> connection check on proxy side that is executed before reusing a connection
> will detect that this socket has been closed by the remote side.
> But yes, in theory their remains a race here if the proxy reuses the connection
> faster then the backend needs time to close the socket after sending the response.
> 

+1 on the 'in theory' part, but seeing this in the real world
is very very remote.
-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
	    "If you can dodge a wrench, you can dodge a ball."