IE Content Advisor

[poeee]

I am attempting to allow access to a single website on a PC.

In the past, other PC's have been set up through the Content Advisor in IE to only allow this single website and it works fine for now.

As far as I can see, this new PC i'm setting up has everything set up the same in the content advisor, but it will only give access to the front site, not the complete website (do a search, click a link, etc).

It's a rather detailed website, and setting the content advisor up for each page would be way to involved.

What's the trick for simply allowing the complete page (all pages, folders, etc)? This is how I thought it worked?!

The pages are https pages, if that makes any difference?

[cluberti]

First of all, Content Advisor was never meant to be a _proxy_, it was meant to be used in parental controls. I know there are KB articles on how to do this, but it's not supported, and for valid technical reasons - for one, Content Advisor loads every page you visit (allowed or not) in a hidden browser window, then scans the page to see if it should be allowed or not.

Honestly, the best way to do this is to use a proxy .pac file as the autoconfiguration address in IE, and only allow access to one site (and only to https: traffic to that site), and then point all other traffic somewhere else (like 127.0.0.1).

[ringfinger]

I use content advisor on a couple PCs in my network which cannot pass through our normal proxy.pac. To allow access to the entire website, as long as the original domain name stays the same I use a wildcard. Example: http://www.cnn.com/* . Like i said though, if there are any redirects to another domain name, CA will pick it up. Good luck.

[poeee]

I use content advisor on a couple PCs in my network which cannot pass through our normal proxy.pac. To allow access to the entire website, as long as the original domain name stays the same I use a wildcard. Example: http://www.cnn.com/* . Like i said though, if there are any redirects to another domain name, CA will pick it up. Good luck.

Cheers mate, fixed the problem! I had tried the wildcard, but only on the http URL, not the https.

I know it's not the best way to limit accessability, but it was the way it was set up before I started here, and we've had no issues with people abusing it. If the issue comes up in the future, then a more secure option will be implemented.