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 11:42:46 -08:00
parent 782af8c8cf
commit fef7db6764
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Dynamic-filtering:-rule-syntax.md

@ -1,3 +1,11 @@
### Rule syntax
A dynamic filtering rule is made of four components: a source hostname, a destination hostname, a request type, and then a keyword which tells what to do with a request which happens to match the three former components.
source-hostname destination-hostname request-type action
Source hostname always correspond to the hostname extracted from the URL of the web page in the browser. The destination hostname correspond to the hostname extracted from the URL of a remote resource which the web page is fetching (or trying to). The type is the type of the fetched resource. A request can be blocked, allowed, or ignored.
### Type-based rules
Type-based rules are used to filter specific types of request on a web page. There currently exists five types of request which can be dynamically filtered:
@ -10,7 +18,7 @@ Type-based rules are used to filter specific types of request on a web page. The
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 "block 3rd-party embedded frames everywhere".
Another example: `wired.com * image block`, which means "block all images when visiting a web page on wired.com".
Another example: `wired.com * image block`, which means "block all images when visiting a web page on wired.com". Note that with type-based rules, the destination hostname is **always** `*`, meaning "from anywhere".
### Hostname-based rules