Mirrors/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2024-09-29 06:07:11 +02:00
Code Issues Releases Wiki Activity

Typos

q1800 2022-04-24 21:43:42 -05:00
parent cdc8c37a3a
commit 6d72b03627
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Dynamic-filtering:-rule-syntax.md

@ -47,7 +47,7 @@ Type-based rules are used to filter specific types of request on a web page. Cur
- `3p-script`: 3rd-party scripts, i.e. scripts which are pulled from a different domain name than that of the current web page
- `3p-frame`: 3rd-party frames, i.e. frames elements which are pulled from a different domain name than that of current web page
These rules can apply everywhere, or be specific to a web site. For instance blocking 3rd-party frames is a very good habit security-wise: `* * 3p-frame block`. This rule translates into "globally block 3rd-party frames".
These rules can apply everywhere, or be specific to a website. For instance blocking 3rd-party frames is a very good habit security-wise: `* * 3p-frame block`. This rule translates into "globally block 3rd-party frames".
Another example: `wired.com * image block`, which means "block images from all origins when visiting a web page on wired.com".
@ -63,7 +63,7 @@ With hostname-based rule, the request type is always `*`, meaning the rule will
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: `wired.com disqus.com * noop`, which means "do not apply dynamic filtering to network 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.
Just like type-based rules, a hostname-based rule can apply only when visiting a specific website, for example: `wired.com disqus.com * noop`, which means "do not apply dynamic filtering to network 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.
***
@ -76,6 +76,6 @@ A matching rule can do one of three things:
- Thus you can use them to block with 100% certainty (unless you set another overriding dynamic filter rule).
- `allow`: matching network request will be allowed.
- `allow` dynamic filters rules override any existing static and dynamic block filters.
- Thus they are most useful to create finer-grained exceptions, and to un-break web sites broken by some static filters somewhere.
- Thus they are most useful to create finer-grained exceptions, and to un-break websites broken by some static filters somewhere.
- `noop`: exclude network requests from being subjected to dynamic filtering.
- It cancels dynamic filtering, but it does not cancel static filtering.