I have a theoretical question regarding a issue i had today.
A user called and said that google-translate was blocked. I couldn't understand that, since i knew that we've allowed that.
I went to http://translate.google.com and sure enough, "Application Blocked".
I went to the monitor tab on the firewall web interface and set a filter for google-translate applications. I was surprised to see that allow/deny actions were 50/50. Some users got a allow, others a deny.
Eventually, by accident, i opened a new browser window and navigated to http://translate.google.dk
We're based in Denmark, so thats the TLD for us.
And woop woop, no problems there.
So I've told my users to use the .dk extension instead..
But what is happening? Why is google's localization system interfering with my application rules ??
We have identified the issue and are working to provide a fix in the next content version.
Content version 259 introduced two new application functions for google-translate, one each for auto and manual.
But traffic to the landing page is neither of these, and may be blocked if you have a deny-all rule at the bottom.
As a workaround, you can revert to content version 258, or, you can create a custom app with a different name (e.g. custom-google-translate) that looks for the pattern “translate.google.com” in the http-req-host-header, and add that app to the allow rule.
It appears that in the 259-1078 application signatures dated 2 Aug 2011, Google Translate may be identified as google-translate or google-plus-base. With these application signatures, even if the google-translate application is permitted, you may still be getting blocks.
In addition, google-translate has been branched out into 3 applications in this version: google-translate, google-translate-auto and google-translate-manual. http://translate.google.com is blocked even allowing all 3 applications.
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!