Hi List,
I know that this seems to be a topic that has been covered before, but even
reading through the archives, i'm still having a few niggling problems with
the setup.
I'm trying to put a reverse squid proxy (squid/2.5/STABLE12) between the
internet and OWA (SBS server).
Client --(https:443)--> squid --(http:80)--> OWA
Everything works fine when it is plain http:80 traffic through the proxy.
Seem to start encountering some errors with the ssl.
I have recompiled squid with the ssl-2_5.patch for the front-end-https
functionality - which I thought would solve most problems.
Config as below:
https_port 443 cert=/etc/squid/ssl/key.crt key=/etc/squid/ssl/key.key
httpd_accel_host 192.168.1.1
httpd_accel_port 80
httpd_accel_single_host on
httpd_accel_with_proxy on
httpd_accel_uses_host_header on
cache_peer 192.168.1.1 parent 80 0 no-query proxy-only login=PASS
front-end-https=on
squid runs fine, and does not produce any problems, however when I connect
to the proxy, the authentication is fine (which has been set to basic on
IIS). The frameset comes up and two error pages are produced. A warning also
pops up for "non secure pages".
Viewing the source of the frame, the code that IIS produces seems to be
where the problem lies..
<HEAD>
...
<BASE href="http://192.168.1.1/exchange/username/";>
...
</HEAD>
Should that have been re-written as https://192.168.1.1??
Anyone else had any similar problems?
Thanks,
Clark
