You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Joe Orton <jo...@redhat.com> on 2006/02/20 10:43:41 UTC

Re: svn commit: r378032 - in /httpd/httpd/trunk: CHANGES modules/proxy/mod_proxy_http.c modules/proxy/proxy_util.c

On Wed, Feb 15, 2006 at 04:44:43PM -0000, Jim Jagielski wrote:
> Author: jim
> Date: Wed Feb 15 08:44:42 2006
> New Revision: 378032
> 
> URL: http://svn.apache.org/viewcvs?rev=378032&view=rev
> Log:
>   *) mod_proxy: Fix KeepAlives not being allowed and set to
>      backend servers. PR38602. [Ruediger Pluem, Jim Jagielski]
> 
> Also, document previous patch:
>   *) Correctly initialize mod_proxy workers, which use a
>      combination of local and shared datasets. Adjust logging
>      to better trace usage. PR38403. [Jim Jagielski]

This one seems to have broken the proxy tests again, failed tests are:

t/ssl/proxy.t                           172   58  33.72%  3 8 10 12 14 16 18 20
                                                          22 24 26 28 30 32 34
                                                          36 38 40 42 44 46 48
                                                          50 52 54 56 58 115-
                                                          116 118-120 122 124
                                                          126 128 130 132 134
                                                          136 139-140 143-144
                                                          147-148 151-152 155-
                                                          156 159-160 163-164
                                                          167-168 171-172


if I "svn up -r378031 modules/proxy" this goes away.  This looks like a 
lot of reverse proxy-to-SSL-backend tests failing with 502 errors due to 
the proxy failing to negotiate an SSL connection to the backend:

[Mon Feb 20 09:27:50 2006] [info] SSL Library Error: 336130315 
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

(which is the kind of error you get when you try to negotiate SSL with 
something which doesn't speak SSL; perhaps the wrong backend is being 
selected?)

joe