[squid-users] Problems with filtering when using chrome

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14/10/2014 10:26 p.m., Robert Hundley wrote:
> Hi, I'm trying to use squid to do some basic filtering. I have
> added an ACL to filtering based on regular expressions, and added
> in a few strings I'd like not to load. These work correctly on IE
> and firefox, but in chrome the page loads. It correctly records
> TCP_DENIED/403 3674 CONNECT www.dropbox.com:443 - NONE/- text/html,
> but the site then loads regardless.

Not as part of that transaction. Squid emitted a 403 (Forbidden) page.

Do you have a record of that following transaction going through Squid?

> 
> Chrome also seems to struggle with internal hosts; they refuse to
> load even though I have added the nodes to the hosts file, which
> seems to have worked for other browsers.
> 

Hosts file on Squid machine?
 and did you run "squid -k reconfigure" since changing it?

> This originally occurred on 3.1, though I have since updated to
> 3.4.8 and am still experiencing this
> 
> Has anyone come across the same / any similar issues?

It sounds very much like Chrome bypassing the proxy. I have heard of a
few instances where Chrome tried to use a configured proxy then if
that was unsuccessful, went and setup direct TCP connections on its own.

Amos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUPPzdAAoJELJo5wb/XPRj5e0H/36R9c+NVnyHewauuOlY1rn0
QRfkFUewjTAu5HWxX6Fkz9y7jpqrAWZj3IqA2nxwCHRmjUtLaeICYDz371S6FUB/
BmZzF6Mf/9R7sAeqXyj8Kw8E+omvDUenyOg/YDK54Sk7b7AlmpHY23LrCtggDatu
11LB4fg0SygusniQxolsXXQIogAMkyvRiTmQjkLst15uMBY0cAKwdIEkmarKba/a
++HvUKU6aWH6d/rup0kh1N00d9+HWxnvtkFaaT/jw4JNGnnFfcITqRE+wI1T28L1
/RU16cERnQk8IP0JVlzMGDE5NY5wHM6Fl1NR7tjthnEIOaBC8AeZV9lrNNLRUy0=
=XYYf
-----END PGP SIGNATURE-----