Google Ad Services still blocked

Looks to me like your regex meefs a slash before the hypen

[A-Za-z0-9\-]

DouglasFoster said:

Looks to me like your regex meefs a slash before the hypen

[A-Za-z0-9\-]

 

I'm afraid I must disappoint you, but the RegEx is valid (in means of UTM). It's copy&paste from all the other exceptions and valid. But that should be obvious, since I mentioned in my earlier post, that it's working while using the UTM as a proxy.

BR,

Volker

You should use a website override instead of an exception, checking the option for "include subdomains"

Your exception is not being applied, as evidenced by exceptions="" in the logs.   Still thinking about why.

You should use a website override instead of an exception, checking the option for "include subdomains"

Your exception is not being applied, as evidenced by exceptions="" in the logs.   The regex is for the fqdn but tbe match rule is full url.

Cattegory and reputation can be different for different paths under the same host, so it is best to use policy helpdesk with s full utl.

When using the website exception method, I override the category but never the reputation, for safety reasons.  Business is a good generic allow category.

If you don't want to use any existing category, you can create a tag for the website, assign the tag in website overrides, and grant an allow action in tbe filter action(s).  This can be used to grant the override to specific users only, and the tsg becomes the equivalent of a custom category.

DouglasFoster said:

You should use a website override instead of an exception, checking the option for "include subdomains"

Your exception is not being applied, as evidenced by exceptions="" in the logs.   The regex is for the fqdn but tbe match rule is full url.

 

The RegEx matches the domain with any subdomain.

And again: as I told before, the exception is working while using the UTM as a proxy.

Volker, have you tried Doug's suggestion?  It might not be affected by the same bug.  Please let us know if this workaround does what you need to accomplish.

Cheers - Bob

Doug's suggestion may work - it uses a different mechanism to do the same thing.  However if it does it may still be just a workaround.

I will repeat my suggestion:

It might be that the RegEx for UTM and the RegEx for EndPoint is not parsed the same (for example whether to include http).
Can you try another RegEx, just a bare "googleadservices\.com" ?

Also, try making sure the Endpoint has a proper copy of the current configuration (I highly doubt this is the issue, but it doesn't hurt).

On your windows computer go to %ProgramData%\Sophos\Web Control\Policy (yes put %ProgramData% in the path).

Delete all files in the \Policy directory.

Wait a few minutes, files will reappear.

Test again.

so I made the changes as suggested, since my Broker was working this morning ....

and this works. But, as you all said, it is just a workaround and no solution to the functions provided but not working.

Question regarding this workaround: does this only overwrite the "URL Filter" or in addition any other checks made by the UTM/Endpoint?

BR,

Volker

This applies only to Web Filtering, Volker.

Cheers - Bob

This applies only to Web Filtering, Volker.

Cheers - Bob