rob1976 wrote:I want to allow one site access, and there are many other sites linked to this site, I also want to allow these linked sites. Is there any easy way to do that?
The surest way to do this would be to add all those links in a WWW Proxy Server Policy. You can use the Ban List as an effective white list by setting:
"This criterion is NOT met if HTTP_URL contains site.com"
Alternatively, you can setup multiple Filters and Criterion on the Advanced Policy page. That is the surest way to do it, but when you are looking at a site with a lot of links that could be a bit time consuming, which is what I'm guessing you're trying to avoid.
There is another, perhaps slightly sneakier way to do this. If you know that people will always use that main site to visit it's linked sites, you can use HTTP Header checks in the Advanced Policies. Unfortunately this field is optional, so it is not guaranteed to give you that field, but it might work in this case. I tested it as follows:
1. Create a policy for Everyone in WWW Proxy Service.
2. Set the "Default Rights (System Policies) to "Are Ignored"
3. In Advanced create a Filter with one criterion "HTTP URL contains forums.qbik.com". This allowed me access to visit the forums and I could go to "Forums", "FAQ" and "Search" off the forums page. This was the "main" site in your request.
4. Create a second Filter with one criterion "HTTP Header field
referer contains qbik.com". This meant any site I visited when referred from qbik.com was valid and allowed. So from my forum page I could go to the "Qbik Home" link, as that was referred by a site containing "qbik.com". It did not match the condition specified in 3 though. And any attempt to visit "www.google.co.nz" or other sites was met with an access denied policy.
The snag with this is that the field is not always set. It will be, most of the time, but not always. And, if somebody types the link directly or uses their browser history this won't work. (As there won't be a referer)