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/[EMAIL PROTECTED]
> >> 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
