Transparent Proxy and HEAT.NET

The local ISP here is using Squid in a transparent-proxy configuration. They
use a router to redirect all port 80 traffic to the Squid machine. The
problem is that users are failing to log into Heat.Net, a multiuser gaming
site. It appears that during the login, there is a shift from HTTP to HTTPS
and if the IPs do not match during that switch, the user is not allowed to log
in and an "IP mismatch" error is given. I assume that this is occuring
because the HTTP traffic is getting routed through Squid and the HTTPS traffic
is not, correct?

What is the best workaround for this? Would adding something to the Squid
configuration fix it? Or would that not help since even if Squid didn't cache
it or was told to ignore it, it would still be passed along from a different
IP than the HTTPS traffic, correct? If so, then is the best solution to edit
the router redirection and tell it to send all port 80 traffic EXCEPT that for
heat.net to the Squid box -- and therefore let the HEAT.NET traffic continue
directly?

Thanks!

 - John Goggan...
Received on Tue Dec 15 1998 - 14:02:20 MST