topic Blocking by AppID don't work as expected in General Topics

Blocking by AppID don't work as expected

User_333 — Thu, 10 Nov 2011 12:31:01 GMT

To block a webpage like Facebook, I have the follow two possibilities.

1) Block it by the Url Filter

2) Block it by the AppID

Since the URL Filter just looks at the URL and no other content. Access to Facebook will only be blocked if I try to access it by "www.facebok.com". But access via "http://translate.googleusercontent.com/translate_c?hl=de&rurl=translate.google.ch&sl=de&tl=en&u=http://www.facebook.com/&usg=ALkJrhh_Iem_Ly3suOQ6H0aOBboI4hw4wg" will not recognize it as the Facebook URL --> no blocking

If I use the AppID to block Facebook, I am expecting even blocking this Google translate URL since the content is still Facebook. But this isn't the case. I don't get any Facebook app in my traffic log.

So, what is the exact difference between URL Filtering and AppID's (for "Website"-AppID's) and how can I block all this even if the user uses Google translate?

Re: Blocking by AppID don't work as expected

mrajdev — Wed, 23 Nov 2011 01:59:13 GMT

As far as I know chaining of url via google translate will not block for both url and app-id. I would suggest to contact your system engineer to check on this and put in a feature request if it is not currently supported.

Thanks

Re: Blocking by AppID don't work as expected

DavePalo — Wed, 23 Nov 2011 11:20:41 GMT

Hi,

As a temporary workaround, I've recently found that if you were to create a custom URL category containing "*.facebook.com" it would match both "www.facebook.com" and "http://translate.googleusercontent.com/translate_c?hl=de&rurl=translate.google.ch&sl=de&tl=en&u=http://www.facebook.com/&usg=ALkJrhh"

Regards,

Dave