prehistoric-systems/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2026-03-11 09:04:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Dynamic filtering: rule syntax (markdown)

gorhill 2014-12-31 12:45:12 -08:00
parent c34b9262b6
commit c6c843903d
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
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]
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.