https://bz.apache.org/bugzilla/show_bug.cgi?id=37355
--- Comment #13 from Michael Göhler <[email protected]> --- (In reply to Hendrik Harms from comment #12) Thanks for your reply! > You don't need this patch for your setup - no user/password is configured in > ProxyRemote. Only the patches of Bug 57139 and may be of Bug 55892 are > needed for your setup. I know. It was just the easiest way to combine both. > The 502 usually indicates a problem during establishing the TCP connection. > What does the squid do with idle connections? Do you have a firewall in your > setup or other routing devices dropping their routing informations without > TCP-close after an idle timeout? I have a 120 sec. timeout on squid which matches what we see. The Apache correctly identifies the connection as stale and reestablishes it. AH00951: HTTPS: backend socket is disconnected. AH00949: send_http_connect: response from the forward proxy: HTTP/1.0 200 Connection established It seams to be an SSL handshake issue, as the second request logs: [ssl:info] AH01964: Connection to child 0 established (server my.server.name:80) [ssl:debug] ssl_engine_kernel.c(1378): AH02275: Certificate Verification ... while the first logs: [ssl:info] AH01964: Connection to child 0 established (server my.server.name:80) [ssl:info] AH02003: SSL Proxy connect failed I'll go for some LogLevel=trace3 logs, as the error seams to happen in SSL_connect(). Just a side-note: Are you aware of the discussion in Bug 55892? They decided to go without the force-proxy-request-1.0 condition, which is still part of your patch. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
