Blocking a site not working

[clinthammer]

I followed these instructions:
http://support.qbik.com/index.php?_a=kn ... %3C%2Fa%3E

to block a site where http url contains xoxide (just for testing purposes).

Policy applied to everyone. All users connect via www transparent proxy and are assumed users.

I saved the changes and still users can visit sites with xoxide in the url.

Have i done something wrong?

[Pascal]

What was the setting for System Policies? By default they are set to be an alternative to the per-service policies. If you do not specifically exclude them they will grant access.

[clinthammer]

Well i figured the problem.

In the Advanced I had:

Filter name: Regular sites not allowed
Criterion: Not HTTP URL contains "darude"
Not HTTP URL contains "darude"

Filter name: Adult sites not allowed
Criterion: Not HTTP URL contains "bigtimegals"

--
So basically having two filters would not work. I had to put all criterion in one filter...

Is this a bug?

Or are we only allowed to have separate filters if the criterions is different..
e.g one filter with criterion for HTTP URL. then another for HTTP Protocol?

[Pascal]

Refer to your other post on blocking people. Filters are treated as OR statements. So, Filter1 OR Filter2 must be true for the right to be granted. Conditions within a Filter are AND statements, so Condition1 AND Condition2 within Filter1 must be true for the right to be granted.

In your case this would have read as:

If the HTTP URL did not contain "darude" OR if the HTTP URL did not contain "bigtimegals" the right is granted.

When you visited "darude" the second Filter would have been true (The HTTP URL does not contain "bigtimegals") and the right would have been granted. When you visited "bigtimegals" the first Filter would have been true (The HTTP URL does not contain "darude") and the right would have been granted.

So not a bug, by design. It's just a case of how you structure them then.