Nicolás: Good Day,
I have a question, in the Web Control Policy I have the WhatsApp web allowed but in some cases it does not take the permission and blocks it ERR_SSL_PROTOCOL_ERROR
Even if a manual update is done, it does not take the permissions, it is necessary to delete the history (Cache) for the page to reload, my question is why is this happening?
CAN YOU HELP ME WITH THIS QUESTION ?
Hello Nicolas,
Thank you for reaching out to the Sophos Community Forum.
I'd like to ask what web browser is being used when you’re seeing these errors?
Are you seeing any "Website Blocked" messages from Sophos when the error page is returned?
With the current iteration of Web Control, this is the behavior that you will experience. If the site is originally blocked, the web browser will cache the last response from the site and present this when attempting to go to the site again. It's not possible for Sophos to change how the browser will behave.
If this occurs to you and you choose to unblock the website via the policy, you can use an "Incognito" or "In-Private-Browsing" window where the previously cached webpage will not be shown. A reboot or clearing the cache will work to resolve this as you've experienced.
I was able to test this a bit further with the "Early Access Program" and I am able to browse to the site almost right-away after having unblocked it via the policy (verifying the policy changes are received on the endpoint first). I'd recommend enrolling a test device in the EAP group to see if the newest iteration of Web Control behaves a bit better for you.
With the current iteration of Web Control, this is the behavior that you will experience. If the site is originally blocked, the web browser will cache the last response from the site and present this when attempting to go to the site again. It's not possible for Sophos to change how the browser will behave.
If this occurs to you and you choose to unblock the website via the policy, you can use an "Incognito" or "In-Private-Browsing" window where the previously cached webpage will not be shown. A reboot or clearing the cache will work to resolve this as you've experienced.
I was able to test this a bit further with the "Early Access Program" and I am able to browse to the site almost right-away after having unblocked it via the policy (verifying the policy changes are received on the endpoint first). I'd recommend enrolling a test device in the EAP group to see if the newest iteration of Web Control behaves a bit better for you.
