Getting a site recatagorized that has "proxy" as part of it's name? www.proxyvote.com

There are two ways in XG v16.

Web > Categories, Add
Call it "Sites that should be Allowed".  Put in domain name.
In the Policy, create a high level rule that says things of that category are allowed.

Web > URL Groups, Add
Call it "Sites that should be Allowed".  Put in domain name.
In the Policy, create a high level rule that says things of that category are allowed.

Yes...  we have both Custom Categories and URL Groups that effectively do the same thing.

So right now under Protect -> Web -> Exceptions I made a "Sites to Allow Through" rule with the description "Sites being incorrectly blocked".  I had another come up, also categorized as a anonymizer for some reason, that I've added:

Exceptions are another way of allowing things.  It is a bigger hammer, more exact because you can use regex (though more dangerous if you write it incorrectly), but is also turns off other checks such as filetype blocking.  They also automatically apply to every policy.

URL Groups or Custom Categories are more precise in resolving the specific category issue.

Exceptions get evaluated on every single request.  Badly written RegEx can be inefficient.  Hundreds of inefficient RegEx could affect performance on every single request.  URL Groups are more efficient - they still get applied to every request but straight text matches on domain names are much faster.  Custom Categories are the most efficient.  That being said, excluding poor RegEx we are probably talking microseconds.

One difference is in reporting and logging.  The Custom Category would appear in the report.  A URL Group or Exception would still have the original category.

For you, that regex looks good and if you only have a few dozen then it should be fine in Exceptions.

Exceptions are another way of allowing things.  It is a bigger hammer, more exact because you can use regex (though more dangerous if you write it incorrectly), but is also turns off other checks such as filetype blocking.  They also automatically apply to every policy.

URL Groups or Custom Categories are more precise in resolving the specific category issue.

Exceptions get evaluated on every single request.  Badly written RegEx can be inefficient.  Hundreds of inefficient RegEx could affect performance on every single request.  URL Groups are more efficient - they still get applied to every request but straight text matches on domain names are much faster.  Custom Categories are the most efficient.  That being said, excluding poor RegEx we are probably talking microseconds.

One difference is in reporting and logging.  The Custom Category would appear in the report.  A URL Group or Exception would still have the original category.

For you, that regex looks good and if you only have a few dozen then it should be fine in Exceptions.

Thank-you for your reply.  That makes sense.  I'll leave it as is unless we start getting a bunch of these in which case I'll follow your directions.

-Allan