SSLProxyMachineCertificateFile directive behavior

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

SSLProxyMachineCertificateFile directive behavior

Scott Kirby
Hi folks,

Does using the SSLProxyMachineCertificateFile directive have any effect on connections that do NOT require certificate-based client authentication?  For example, if I am using Apache as a proxy to two distinct service endpoints like so (within the same VirtualHost definition):

SSLProxyEngine on
SSLProxyMachineCertificateFile /path/to/client/cert

#Does NOT require client auth
ProxyPass               /foo/ https://host1/foo/
ProxyPassReverse        /foo/ https://host1/foo/

#Requires client auth
ProxyPass               /bar/ https://host2/bar/
ProxyPassReverse        /bar/ https://host2/bar/

And only the host2 requires client-authentication, SSLProxyMachineCertificateFile would presumably not effect traffic to the host1, correct?  Thanks in advance,

Scott Kirby
Interoperability Developer
PCC - Physicians Computer Company
[hidden email]

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]