On Tue, 15 Dec 1998, John Goggan wrote:
> 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?
Heheh. Small world. I used to work there about 6months ago and wrote up
quite a bit of documentation on the whle proxy/firewall with HEAT.NET.
Yes, basically you have to have a direct connection to them, the
webservers will reject with then mentioned error when the IP for the SSL
socket does not match the IP for the HTTP socket. This of course could
have changed since I have been there but it sounds like the exact same
thing..
cheers and good luck,
-
jason
Received on Tue Dec 15 1998 - 15:08:34 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:43:39 MST