https://bz.apache.org/bugzilla/show_bug.cgi?id=63430
--- Comment #4 from Ruediger Pluem <[email protected]> --- (In reply to mark from comment #3) > technically, there was a restart between those sets of lines, but not > between these, I have inserted the "resuming operation" and "mod_ssl" lines > from the global log as well for comparison > > [Tue May 14 09:27:15.212161 2019] [ssl:info] [pid 781991:tid > 140222231095040] AH01876: mod_ssl/2.4.39 compiled against Server: > Apache/2.4.39, Library: OpenSSL/1.0.2r > [Tue May 14 09:27:15.252246 2019] [ssl:debug] [pid 781991:tid > 140222231095040] ssl_engine_init.c(1582): AH02207: loaded 1 client certs for > SSL proxy > [Tue May 14 09:27:15.252487 2019] [ssl:debug] [pid 781991:tid > 140222231095040] ssl_engine_init.c(1582): AH02207: loaded 1 client certs for > SSL proxy > [Tue May 14 09:27:15.253510 2019] [ssl:debug] [pid 781991:tid > 140222231095040] ssl_engine_init.c(1582): AH02207: loaded 1 client certs for > SSL proxy > [Tue May 14 09:27:29.269928 2019] [mpm_event:notice] [pid 781991:tid > 140222231095040] AH00489: Apache/2.4.39 (Unix) OpenSSL/1.0.2r > mod_fcgid/2.3.9 mod_auth_kerb/5.4 mod_qos/11.62 mod_jk/1.2.46 configured -- > resuming normal operations > [Tue May 14 09:37:43.553029 2019] [ssl:warn] [pid 799222:tid > 140218148460288] AH02268: Proxy client certificate callback: (dw25136:11719) > downstream server wanted client certificate but none are configured > > The configuration is pretty big, but the relevant configuration just involves > > <Proxy balancer://balancer2> > SSLProxyMachineCertificateFile /path/to/cert.pem > </Proxy> > > and a later proxypass line. What is the ProxyPass line? Which URL triggers the AH02268? The AH01876 appears 3 times. So you have 2 further Proxy sections that contain SSLProxyMachineCertificateFile? It did work with 2.4.x? -- 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]
