On Tue, Jan 08, 2008 at 08:37:10PM +0100, Ruediger Pluem wrote: > > Very, very strange because in the SSL proxy forward case you > > 1. use mod_proxy_connect which wasn't touched in 2.2.x for the last 11 month, > so I doubt that this is a regression-
I must confess that I have always tested the proxy as a forwarder, and only found the bug now. It may have been lingering there for a long time already. > 2. The HTTP_IN filter does not do anything in the SSL proxy forward case (it > is not in the filter chain) as in contrast to non SSL proxying > mod_proxy_connect > does not care about the contents of the backend at all and is a pure data > pump > on TCP level. Then perhaps the patch really did not change it at all, and I only happened to get a few successful connections after having tried the patch (and would have gotten them without it, too, had I tried hard enough :-) > Or are you talking about reverse proxying a SSL backend? Nope, this is the forward proxy situation. SSL-Browser <--CONNECT--> httpd-2.2.7-proxy <--> origin server Martin -- <[EMAIL PROTECTED]> | Fujitsu Siemens http://www.fujitsu-siemens.com/imprint.html | 81730 Munich, Germany
