Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 8 subscribers
  • Views 3967 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM SG210 Web Filtering not Working with Chrome

Erik Puscher

Hello,

we had setup "Web Filtering" on our SG210 and are using the "Proxy Auto Configuration".

For testing i browse to a forbidden website.

Firefox and Edge are blocking the content correctly.

But Chrome does not.

Proxy settings are rolled out via GPO.

As far as i can see, all is set up correctly. Windows Internet Options are pointing to the correct wpad.dat. The wpad.dat code seems correct since Firefox and Edge are blocked.

I found the following in the discussions. But i can't find such an option on our SG210.

 Web filtering not working with chrome 

Do you have any clues?



This thread was automatically locked due to age.
Parents
  • 0

    Hi,
    Chrome browsers are also filtered in my environments like other browsers.
    But Google implements some "privacy optimizations". (like Apple his privacy proxy)
    Here the DNS requests or the complete web requests use a tunnel (VPN) .
    So your firewall can't see anything.
    Here, the “quick protocol” is usually used.
    You can try blocking  “quick protocol” within your rules.
    .... but maybe there is something new ... from the "security sheriff google"


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply
  • 0

    Hi,
    Chrome browsers are also filtered in my environments like other browsers.
    But Google implements some "privacy optimizations". (like Apple his privacy proxy)
    Here the DNS requests or the complete web requests use a tunnel (VPN) .
    So your firewall can't see anything.
    Here, the “quick protocol” is usually used.
    You can try blocking  “quick protocol” within your rules.
    .... but maybe there is something new ... from the "security sheriff google"


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
Unfiltered HTML