Henrik Nordstrom-5 wrote:
>
> 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
>
>
>
am i getting this wrong, or does that mean, that we don´t need to specify a
sslcert in the cache_peer line?
should he connect to the sharepoint with ssl when i just use that??:
cache_peer 10.xxx.xxx.xxx parent 443 0 ssl no-query originserver login=PASS
front-end-https=on name=*.*.com
--
View this message in context:
http://www.nabble.com/squid-3.1%3A-How-to-setup-a-Squid-SSL-reverse-proxy-for-a-parent-SSL--Squid-proxy--tp24911339p24920234.html
Sent from the Squid - Users mailing list archive at Nabble.com.
