Mirrors/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2024-07-08 12:57:57 +02:00
Code Issues Releases Wiki Activity

Add to= and from= network filter options

MasterKia 2022-12-29 11:45:00 +03:30
parent 7e5af9ed1b
commit 184596103f
1 changed files with 38 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
Static-filter-syntax.md

@ -286,7 +286,9 @@ Filter list authors are discouraged from using exception filters of the `cname`
***
#### `denyallow`
#### ~~`denyallow`~~
**Superseded by [`to`](#to).**
New in [1.26.0](https://github.com/gorhill/uBlock/commit/c3bc2c741d61db3e99b313835c2ae34a4a008359).
@ -324,6 +326,8 @@ See also: [`all`](#all)
#### `domain`
Alias: [`from`](#from)
Restrict the filter to be applied only to the specified domain(s).
Use the `|` symbol to join multiple domains.
@ -364,6 +368,16 @@ Equivalent to `subdocument` [option](https://help.eyeo.com/en/adblockplus/how-to
***
#### `from`
New in [1.46.1b0](https://github.com/gorhill/uBlock/commit/19f8b30d577ac17097b8060adfc92093866e26d8).
It is just an alias for the `domain=` option. The logger will render `domain=` network filters using the `from=` version.
See: [`domain`](#domain)
***
#### `generichide`
Alias: `ghide`.
@ -528,6 +542,29 @@ For example:
***
#### `to`
New in [1.46.1b0](https://github.com/gorhill/uBlock/commit/19f8b30d577ac17097b8060adfc92093866e26d8).
Solves [uBlockOrigin/uBlock-issues#2412](https://github.com/uBlockOrigin/uBlock-issues/discussions/2412).
The main motivation of this option is to give uBO's static network filtering engine an equivalent of DNR's [`requestDomains`](https://developer.chrome.com/docs/extensions/reference/declarativeNetRequest/#property-RuleCondition-requestDomains) and [`excludedRequestDomains`](https://developer.chrome.com/docs/extensions/reference/declarativeNetRequest/#property-RuleCondition-excludedRequestDomains).
`to=` is a superset of `denyallow=` with support for Entity-based syntax and also negated hostname.
For now `denyallow=` won't be deprecated, which still does not support entity-based syntax and for which negated domains are not allowed.
Examples:
```
||it^$3p,to=~example.it
*$script,from=beforeitsnews.com,to=google.*|gstatic.com
```
See also: [`denyallow`](#denyallow), [`from`](#from)
***
#### `xhr`
Equivalent to `xmlhttprequest` [option](https://help.eyeo.com/en/adblockplus/how-to-write-filters#options). For convenience.