There are a few other caveats to keep in mind with squidGuard for this sort of job:
1 - HTTPS proxying is implemented using the CONNECT method. A CONNECT url has no path information in it, so you can only do domain-wide rules. I guess this means also if you ALLOW isp.com, but DENY isp.com/nasty/, https://isp.com/nasty/ will slip by ALLOWed. 2 - since CONNECT URLs aren't supposed to have the PROTO:// part on them, and only ever one colon, squid can get really confused about redirect 302:bla.com style redirects. On Wed, 6 Mar 2002, Joe Cooper wrote: > Note that you /can/ proxy https with Squid (and then it will work, I > think) but you can't do it with Squid acting as a transparent or > interception proxy. > > [VL]Sparkz wrote: > > Ok that would be why it don't work. LOL > > Thanks anyway. > > sparkz > > > > > > ----- Original Message ----- > > From: "Chris Hedemark" <[EMAIL PROTECTED]> > > To: "steven" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Wednesday, March 06, 2002 2:03 PM > > Subject: Re: redirection problems https:// > > > > > > > >>On Tuesday 05 March 2002 05:07 pm, steven wrote: > >> > >>>Hi guys > >>>everything seems to be working fine except > >>>say Http://www.google.com is restricted using the google.com in the > >>> > > domains > > > >>>file https://www.google .com is let through how can i stop this. > >>> > >>>its letting through https:// secure websites > >>> > >>>thanks sparkz > >>> > >>Typically https doesn't even go through squid. > >> > >> > > > > > > > > > > -- > Joe Cooper <[EMAIL PROTECTED]> > http://www.swelltech.com > Web Caching Appliances and Support > >
