From c34b9262b6c9c30f8ae3faa057a40b6b691a0c7e Mon Sep 17 00:00:00 2001 From: gorhill Date: Wed, 31 Dec 2014 12:06:04 -0800 Subject: [PATCH] Updated Dynamic filtering: rule syntax (markdown) --- Dynamic-filtering:-rule-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dynamic-filtering:-rule-syntax.md b/Dynamic-filtering:-rule-syntax.md index 1db8719..6f057c2 100644 --- a/Dynamic-filtering:-rule-syntax.md +++ b/Dynamic-filtering:-rule-syntax.md @@ -30,4 +30,4 @@ With hostname-based rule, the type is always `*`, meaning the rule will apply to For example, `* linkedin.com * block` means "globally block all net requests to `linkedin.com`". -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 +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. [Changing my mind... 1st-party requests should never be evaluated against hostname-based rules] \ No newline at end of file