[squid-users] unable to access owa back end over https

Folks,

I have done the work and set up a squid reverse proxy to access an
internal Microsoft OWA server. This all works fine I make the
connection between the squid reverse proxy and the OWA server plain
HTTP, if I try to force the back end communication to be HTTPS only
then it does not work, by this I mean the browser sits there waiting
and eventually times out.

Doing a packet sniff on the interfaces, I see squid make the request
to owa, owa replies with a single packet and then there is no more
traffic. If I run a browser on the machine that hosts the reverse
proxy and try to connect to the owa backend using https in that
browser then owa works fine - it seems like squid is failing to
negotiate the https connection somehow. There is nothing in the logs
I can see that indicate a problem.

Any suggestions? Or am I stuck with a http only backend service?

I am running squid-2.5-stable7+reverse_proxy_patch on a Solaris 9
machine.

-- 
Brett Lymn