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: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Mon, 20 Feb 2006 10:50:08 +0000
From: Joe Orton <jorton@redhat.com>
To: dev@httpd.apache.org
Subject: Re: svn commit: r378032 - in /httpd/httpd/trunk: CHANGES
 modules/proxy/mod_proxy_http.c modules/proxy/proxy_util.c
Message-ID: <20060220105008.GB10923@redhat.com>
Mail-Followup-To: dev@httpd.apache.org
References: 
 <F6E88684A95CDB4DBBD5B9F4C1C4B09B020EB0FB@vis01-mx02.vis.internal.vodafone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <F6E88684A95CDB4DBBD5B9F4C1C4B09B020EB0FB@vis01-mx02.vis.internal.vodafone.com>
User-Agent: Mutt/1.4.2.1i

On Mon, Feb 20, 2006 at 11:30:02AM +0100, Plüm, Rüdiger, VIS wrote:
> 
> 
> >> -----Ursprüngliche Nachricht-----
> >> Von: Joe Orton 
> >> > 
> >> http://mail-archives.apache.org/mod_mbox/httpd-dev/200602.mbox
> /ajax/%3c035587A0-586B-4BD7-A4F3-9D76D5B89552@jaguNET.com%3e
> >> this is really weird. Maybe another change that happened after r378032?
> >
> >Maybe Jim's build didn't include mod_ssl?  r378032 is the most recent 
> >change to modules/proxy.
> 
> Maybe. Got another idea in the meantime. Maybe it is because we use the same
> socket to a backend, but we create a new conn_rec each time for this backend
> and thus try to reinit the existing ssl connection. Could you please give the
> following patch a try?

That fixed most of the failures, there are still two left:

t/ssl/proxy....ok 61/172# Failed test 62 in t/ssl/proxy.t at line 112 
fail #2
t/ssl/proxy....ok 112/172# Failed test 113 in 
/local/httpd/pf-trunk/blib/lib/Apache/TestCommonPost.pm at line 131 fail 
#102
t/ssl/proxy....FAILED tests 62, 113
        Failed 2/172 tests, 98.84% okay

I found only one pertinent error message in the log:

[Mon Feb 20 10:40:08 2006] [debug] proxy_util.c(2118): proxy: HTTP: 
connection complete to 127.0.0.1:8529 (localhost.localdomain)
[Mon Feb 20 10:40:08 2006] [error] (32)Broken pipe: proxy: pass request 
body failed to 127.0.0.1:8529 (localhost.localdomain)
[Mon Feb 20 10:40:08 2006] [error] (32)Broken pipe: proxy: pass request 
body failed to 127.0.0.1:8529 (localhost.localdomain) from 127.0.0.1 ()

...perhaps a persistent connection being closed by the backend, and the 
proxy only finding out about this half way through sending a request 
body?  Hard to handle that in the proxy - probably best to just 
ungracefully terminate the connection to the client in that case, it 
should then resend appropriately too.

joe