tis 2009-08-11 klockan 02:38 -0700 skrev chrischni:
> this is our cache_peer config:
>
> cache_peer 10.xxx.xxx.xxx parent 443 0 ssl no-query originserver login=PASS
> front-end-https=on sslkey=//usr/newrprgate/CertAuth/sslkey.key
> sslcert=//usr/newrprgate/CertAuth/sslcert.cert name=*.*.com
Probably it's not recognising the issuing CA. The sslkey & sslcert
options to cache_peer is for using a client side certificate for
authenticating to the webserver (if requested by the webserver) and is
not used for verifying the authenticity of the webserver.
Regards
Henrik
Received on Tue Aug 11 2009 - 15:32:31 MDT
This archive was generated by hypermail 2.2.0 : Tue Aug 11 2009 - 12:00:02 MDT