RE: [squid-users] rpc over http problems

> 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
>
>
> The OWA config works and I'm trying to add rpc over http. OL will not
> connect and nothing shows up in access.log. Running tcpdump on the
> external port on the squid box, I see incoming connection attempts from
> the client, but squid seems to be ignoring. Nothing is passed to the
> exchange server.

1) are they going to one of the IP:port squid is listening on?
2) is the firewall blocking/altering them at TCP-level?
3) what does cache.log have to say about the attempts?

>
> Thanks,
> Alan
>
>
> -----Original Message-----
> From: Henrik Nordstrom [mailto:henrik_at_henriknordstrom.net]
> Sent: Monday, May 26, 2008 1:04 PM
> To: Alan Lehman
> Cc: squid-users_at_squid-cache.org
> Subject: Re: [squid-users] rpc over http problems
>
> On mån, 2008-05-26 at 12:48 -0500, Alan Lehman wrote:
>
>> cache_peer ip_of_exchange parent 80 0 no-query originserver login=PASS
>> ssl sslcert=/usr/share/ssl/rpc.pem name=exchange_rpc
>
> This tells Squid that it should use SSL encryption to connect to the peer
> on port 80. Looks wrongto me.
>
> Remove the ssl and sslcert options, and replace them with
> front-end-https=auto instead. Should match yout requirements better..
>
> Regards
> Henrik
>
Received on Mon Jun 09 2008 - 02:21:36 MDT