Search squid archive

RE: rpc over http problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On sön, 2008-06-08 at 10:57 -0500, Alan Lehman wrote:
> Finally getting back to this. Thanks for the earlier responses. 
> I changed cache_peer to use front-end-https=auto, but no change in behavior.
> 
> This may be a stupid question. I'm wondering if my problem is due to the fact that I'm using the same squid as an accelerator for OWA to the same Exchange box:
> 
> https_port a.b.c.d:443 cert=/usr/share/ssl/combined.crt key=/usr/share/ssl/owa.key defaultsite=owa.xx.com
> https_port a.b.c.e:443 cert=/usr/share/ssl/rpc.pem defaultsite=rpc.xx.com
> 
> cache_peer ip_of_exchange parent 80 0 no-query originserver front-end-https=on login=PASS
> cache_peer ip_of_exchange parent 80 0 no-query originserver login=PASS front-end-https=auto name=exchange_rpc

You only need one cache_peer if you only have a single server.

Regards
Henrik



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux