> 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?
On your Cisco, just add a rule before your redirect to allow (well it's
probably be a deny rule), traffic to the heat.net host so it doesn't
transparently proxy. I'm not too sure if Squid can transparently proxy HTTPS
requests yet.
Jordan
-- Jordan Mendelson : http://jordy.wserv.com Web Services, Inc. : http://www.wserv.comReceived on Wed Dec 16 1998 - 10:46:22 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:43:40 MST