Pull request: all: add $dnsrewrite handling
Merge in DNS/adguard-home from 2102-dnsrewrite to master
Updates #2102.
Squashed commit of the following:
commit 8490fc18179d38c4b162ff9b257fea1f8535afbd
Merge: d9448ddca e7f7799b3
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Dec 21 16:44:00 2020 +0300
Merge branch 'master' into 2102-dnsrewrite
commit d9448ddca6d4ef3635d767e3e496e44c35d3fc6e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Dec 21 15:44:54 2020 +0300
querylog: support dnsrewrite rules
commit 40aa5d30acddf29fb90d249d8806941c6e1915a4
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Dec 18 19:27:40 2020 +0300
all: improve documentation
commit f776a0cd63b1640ba1e5210d9301e2a2801fd824
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Dec 18 19:09:08 2020 +0300
dnsfilter: prevent panics, improve docs
commit e14073b7500d9ed827a151c5b8fb863c980c10e8
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Dec 4 15:51:02 2020 +0300
all: add $dnsrewrite handling
This commit is contained in:
@@ -4,15 +4,21 @@
|
||||
|
||||
## v0.105: API changes
|
||||
|
||||
### New `"reason"` in `GET /filtering/check_host` and `GET /querylog`
|
||||
|
||||
* The new `DNSRewriteRule` reason is added to `GET /filtering/check_host` and
|
||||
`GET /querylog`.
|
||||
|
||||
* Also, the reason which was incorrectly documented as `"ReasonRewrite"` is now
|
||||
correctly documented as `"Rewrite"`, and the previously undocumented
|
||||
`"RewriteEtcHosts"` is now documented as well.
|
||||
|
||||
### Multiple matched rules in `GET /filtering/check_host` and `GET /querylog`
|
||||
|
||||
<!-- TODO(a.garipov): Update with better examples once $dnsrewrite rules are
|
||||
checked in. -->
|
||||
|
||||
* The properties `rule` and `filter_id` are now deprecated. API users should
|
||||
inspect the newly-added `rules` object array instead. Currently, it's either
|
||||
empty or contains one object, which contains the same things as the old two
|
||||
properties did, but under more correct names:
|
||||
inspect the newly-added `rules` object array instead. For most rules, it's
|
||||
either empty or contains one object, which contains the same things as the old
|
||||
two properties did, but under more correct names:
|
||||
|
||||
```js
|
||||
{
|
||||
@@ -30,6 +36,30 @@ checked in. -->
|
||||
}
|
||||
```
|
||||
|
||||
For `$dnsrewrite` rules, they contain all rules that contributed to the
|
||||
result. For example, if you have the following filtering rules:
|
||||
|
||||
```
|
||||
||example.com^$dnsrewrite=127.0.0.1
|
||||
||example.com^$dnsrewrite=127.0.0.2
|
||||
```
|
||||
|
||||
The `"rules"` will be something like:
|
||||
|
||||
```js
|
||||
{
|
||||
// …
|
||||
|
||||
"rules": [{
|
||||
"text": "||example.com^$dnsrewrite=127.0.0.1",
|
||||
"filter_list_id": 0
|
||||
}, {
|
||||
"text": "||example.com^$dnsrewrite=127.0.0.2",
|
||||
"filter_list_id": 0
|
||||
}]
|
||||
}
|
||||
```
|
||||
|
||||
The old fields will be removed in v0.106.0.
|
||||
|
||||
## v0.103: API changes
|
||||
|
||||
Reference in New Issue
Block a user