Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Be notified of Websense news, product information, industry events and more.
We have unblocked the yui.yahooapis.com but it was not being blocked in the first place. Also, it does not matter the user level (unrestricted or normal) so it does not seem to be an issue with the blocking.
Any ideas will be welcome since this site is a necessary site in the organization.
my company is experiencing this problem as well....exactly the same.
very interested to hear if anyone has found a way to fix this.
I just browsed to the zillow.com website and the following categories were "triggered"
If those categories are allowed you should be able to view the site. Is there a section of the website that you use that is a possible a redirect somewhere? or is the site blocked right from the entry page?
Is the site using HTTPS at any stage?
Are you using an integration, integration with network agent or just stand alone installation?
What are you using as a Proxy, we are using ISA and we have had issues with sites containing java on their sites. They have not been blocked by Websense but by ISA. We have had to sometimes create a rule to allow the site. If you have ISA I would create a rule which allows a test pc to the site to see if it loads correctly.
my company is using a Pix 506e, but i'm 100% sure this is not a firewall / proxy issue. the moment websense is offline the site works as the OP first stated. when it comes back online the site stops working.
also, with zillow trigering both real estate and information technology categories, it shouldn't matter if the sites have been unblocked in the category managers?
Are you integrating with ISA, TMG or Squid? Or are you using the PIX integration?
Does the zillow.com page load in the beginning and only when you navigate get blocked... or can you not even get to the entry page?
the page loads everything except for a call to a .js script that run the search bar / function.
Stop your log server, and run the following command:
<path to websense>\bin\testlogserver.exe -onlyip <yourIP>
"<yourIP>" should be your workstation ip address.
On your workstation, close all browsers or programs that may access the internet. Then open a browser and go to www.zillow.com, and try to reproduce the error.
On the server where testlogserver is running a running list of all URL's accessed and permitted or blocked will scroll on the screen. Look to see if you see any blocked URL's. If Websense blocks a url it will be written to the screen. If you do not see any actions of blocked then Websense is not blocking it.
i tried this...for some reason no data ever shows up in the console window...
Unfortunately we are having the same results with this website as well. Shutting Websense down momentarily allowed the site to work properly which clearly indicates where the problem is.
Any help with this would be appreciated!
Fiddler2 says that there is no header coming back from yui.yahooapis.com (Fiddler2 calls it a "stupid site") and I think that is where WebSense is loosing it...
Strange that I don't have
the problem in my lab but I am running in stand alone, possible the
issue only exists with integrations. I reckon you need to log a call with Websense
tech support and get them to look at it... please post response if you find a solution as this is an interesting problem.
This issues sounds very much like the old "Yahoo" page issue with PIX integration.That website also had issues when WebSense was running, but worked when WS was stopped, but was actually still a PIX/ASA firewall issue...
Check the ASA/PIX for the following commands:
filter url http 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 allow longurl-truncate cgi-truncateurl-block url-mempool 10240url-block url-size 4url-block block 128
The "-truncate" commands will cut off overly long url strings that can "choke" websense, and the "url-block" commands give more resources for buffering.
The "allow" command tells the ASA/PIX to permit all Internet access if the WebSense service is not reachable, do not put that line in if you want to default to "Block on failure"...
This might not help at all, but worth a look...
Thank you. I did not have that in the ASA but have added it.
It is after hours now but I will have people give it a try tomorrow.