From 3867bf064e13b8e5549fb74fe0bdf0959cbe35df Mon Sep 17 00:00:00 2001 From: gorhill Date: Wed, 31 Dec 2014 11:51:00 -0800 Subject: [PATCH] Updated Dynamic filtering: rule syntax (markdown) --- Dynamic-filtering:-rule-syntax.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Dynamic-filtering:-rule-syntax.md b/Dynamic-filtering:-rule-syntax.md index de218c5..d5b4e57 100644 --- a/Dynamic-filtering:-rule-syntax.md +++ b/Dynamic-filtering:-rule-syntax.md @@ -24,4 +24,10 @@ Note that with type-based rules, the destination hostname is **always** `*`, mea ### Hostname-based rules -Hostname-based rules are used to filter network resources according the their origin, i.e. according to which remote server a resource is pulled. Hostname-based rules have a higher specificity than type-based rules, and thus hostname-based rules always override type-based rules whenever a network request end up matching both a type- and a hostname-based rule. \ No newline at end of file +Hostname-based rules are used to filter network resources according the their origin, i.e. according to which remote server a resource is pulled. Hostname-based rules have a higher specificity than type-based rules, and thus hostname-based rules always override type-based rules whenever a network request end up matching both a type- and a hostname-based rule. + +With hostname-based rule, the type is always `*`, meaning the rule will apply to any type of request. + +For example, `* linkedin.com * block` means "globally block all net requests to an `linkedin.com` server". + +Just like type-based rules, a hostname-based rule can apply only when visiting a specific web site, for example: `linkedin.com linkedin.com * allow`, which means "allow net requests to `linkedin.com` when visiting a web page on `linkedin.com`. Since this last rule is more specific than the previous one, it will override the global blocking of `linkedin.com` everywhere. \ No newline at end of file