- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
11-10-2011 04:31 AM
Hi
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..." 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?
11-22-2011 05:59 PM
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
11-23-2011 03:20 AM
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..."
Regards,
Dave
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!