Alan Lehman wrote:
>> My current config (which works for OWA, but not RPCoHTTP):
>>
>> extension_methods RPC_IN_DATA RPC_OUT_DATA
>>
>> https_port public_ip_for_owa:443
cert=/usr/share/ssl/owa/combined.crt key=/usr/share/ssl/owa/owa.key
defaultsite=owa.tld.com
>>
>> https_port public_ip_for_rpc:443
cert=/usr/share/ssl/rpc/combined.crt key=/usr/share/ssl/rpc/rpc.key
defaultsite=rpc.tld.com
>>
>> cache_peer ip_of_exchange parent 80 0 no-query originserver
front-end-https=auto login=PASS
>
>You need a second entry for port 443 on the exchange server to handle
>the RPC requests.
>This is where the name= parameter becomes very important and needs to be
>unique for each entry and used in the cache_peer_access lines below.
Thanks for the reply and clarification on the OWA config. My intention
was to pass the RPC to Exchange unencrypted, on port 80. Previously,
either you or Henrik had suggested eliminating one of the cache_peer
lines, since both OWA and RPC would be going to port 80 on Eggchange.
Oh yes, I'd overlooked that earlier mail (wasn't mine). I'm skeptical
that Exchange will allow RPC over non-secure ports. Or if its listening
there, that it would tell clients the port-80 on Squid.
The squid config you had _should_ work for Squid under that setup. I
think form teh non-working state you reported there is something missing
at the Exchange end to get both on port-80.
... if you can get it going over port-80 great. I'd like to know how for
the wiki.
Amos
--
Please use Squid 2.7.STABLE2 or 3.0.STABLE6
