Monday, December 23, 2024 12:11:55 AM

White Listing

10 years ago
#2072 Quote
Here are more Allowed Sites URLs that are needed for your list:

http://www.starfall.com/*

http://www.spellingcity.com/*
http://platform.twitter.com/*
https://platform.twitter.com/*
http://ct1.addthis.com/*

http://www.facebook.com/*

Also, please download the latest build of Secure Lockdown - Internet Explorer Edition. THere have been some improvements regarding the "Content Advisor" message and page load speed when using this feature.
0
10 years ago
#2073 Quote
Thanks allot for the help on all this, it is greatly appreciated. I tried using the "View Source" feature in IE 11 and it did not actually show doubleclick.net for pbskids.org, so I am hopeful that the Content Advisor warning will.
I have the latest version of the product, unless changes have been made to it in the last few days.
I have reservations about using Google Chrome due to privacy concerns and it's policies for transfer of private information, but it may turn out to be what I end up using based on the difficulties with IE 11 and Content Advisor.
0
10 years ago
#2074 Quote
The difficulties with IE 11 Content Advisor and the number of additional sites required that just kept popping up over and over again, which caused Inteset Secure Lockdown v2 - Internet Explorer Edition to have to be stopped and restarted over and over again has made the decision for me to just go ahead and use the Google Chrome version.
0
10 years ago
#2077 Quote
Note that many public sites have links to external URLs. There could be an endless series of websites you would need to whitelist. So, if you allow access to a site with many external links, the "Content Advisor" message is unavoidable. In Chrome, you will get a similar message if a user clicks on a link where the URL is not allowed (not whitelisted). If you allow the display of the navigation buttons, the user could click on the back button to get to the previous page and the browser would not need to be closed/reopened.
0
8 years ago
#3410 Quote
EDIT: I've found the issue, "No Browser Close" for some reason is causing the issue and giving me restrictions for some reason.

I'm using Secure Lockdown IE Edition. Once I enabled whitelisting by mistake I keep receiving restrictions even with it disabled. So I've inspected my websites network activity and whitelisted every possible URL it may try and call to and I'm still receiving restrictions. I'm running IE in maximized with only Nav buttons being shown. Is there a way to restore Secure Lockdown to it's default original settings? I've deactivated and tried uninstalling and reinstalling but I'm not sure where it keeps the settings stored.
0
8 years ago
#3412 Quote
If you want to disable the white listing, disable the "Enable" check box on the IE Lockdown > Allowed Sites tab.
0
8 years ago
#3413 Quote
Inteset S. wrote:
If you want to disable the white listing, disable the "Enable" check box on the IE Lockdown > Allowed Sites tab.


Understood, I got it to a workable state. However I don't understand why the "No Close Browser" would throw a restriction and not allow people to navigate away from the homepage of the website. If they try to drill down into a category or click on any link on our website it gives them the restriction notification.
0
8 years ago
#3414 Quote
That feature does not allow the browser window to be closed which is what the webpage is attempting to do.
0
8 years ago
#3417 Quote
By going to another page of the website it's attempting to close the browser? The functionality seems pretty broken then. It's simply trying to go from www.WEBSITE.com to www.WEBSITE.com/product why would that constitute as a browser window closing? It's staying in the browser but just loading a new page. If that's the case I think it needs to be addressed to somehow fix that so you can have it so the browser can't be closed but can navigate between pages on the same website.
0
8 years ago
#3418 Quote
Try disabling the "IE Lockdown > General Options > No New Window" option. If the new page opens in a new window, that would cause the same message.
0