Re: [squid-users] exchange 2k and 2.5 ssl reverse proxy

OWA knows about a custom Front-End-Https header for this purpose.

The SSL update to Squid-2.5 adds partial support for this header via the
cache_peer directive and may work for your purposes (combine cache_peer
to the OWA server and never_direct to have the requests forwarded via
cache_peer in an accelerator).

Things are a little more obvious in the upcoming Squid-3.0 release
however..

Regards
Henrik

mailinglists wrote:
>
> Hi
>
> I'm a bit stuck in squid 2.5 ssl reverse proxying
> of exchange 2k. However, I can revese proxy tcp:80
> with no problems at all. Works perfect. But as soon
> as I try to use ssl the exchange switches back to
> tcp:80 obviously because it doesn't know about the
> tcp:443 connection user <-> squid. Squid <-> Ex2k OWA
> is tcp:80. Is there a way how I could tell (e.g. via
> headers - that's the way apache does it) ex2k that the
> "front end" squid uses https and not http? In that
> case I believe Ex2k would send back the right url information.
>
> thanks,
> Philipp
Received on Tue Apr 01 2003 - 01:06:49 MST