From c6c843903d7e1da2fc1f232ab7e74fe68d5e3561 Mon Sep 17 00:00:00 2001 From: gorhill Date: Wed, 31 Dec 2014 12:45:12 -0800 Subject: [PATCH] Updated Dynamic filtering: rule syntax (markdown) --- Dynamic-filtering:-rule-syntax.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Dynamic-filtering:-rule-syntax.md b/Dynamic-filtering:-rule-syntax.md index 6f057c2..16297dc 100644 --- a/Dynamic-filtering:-rule-syntax.md +++ b/Dynamic-filtering:-rule-syntax.md @@ -28,6 +28,6 @@ Hostname-based rules are used to filter network resources according the their or 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 `linkedin.com`". +For example, `* disqus.com * block` means "globally block all net requests to `disqus.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. [Changing my mind... 1st-party requests should never be evaluated against hostname-based rules] \ 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: `wired.com disqus.com * noop`, which means "do not apply dynamic filtering to net requests to `disqus.com` when visiting a web page on `wired.com`. Since this last rule is more specific than the previous one, it will override the global blocking of `disqus.com` everywhere. \ No newline at end of file