all: sync with master; upd chlog
This commit is contained in:
@@ -4,6 +4,107 @@
|
||||
|
||||
## v0.108.0: API changes
|
||||
|
||||
## v0.107.37: API changes
|
||||
|
||||
### The new field `"fallback_dns"` in `UpstreamsConfig` object
|
||||
|
||||
* The new field `"fallback_dns"` in `POST /control/test_upstream_dns` is the
|
||||
list of fallback DNS servers to test.
|
||||
|
||||
### The new field `"fallback_dns"` in `DNSConfig` object
|
||||
|
||||
* The new field `"fallback_dns"` in `GET /control/dns_info` and `POST
|
||||
/control/dns_config` is the list of fallback DNS servers used when upstream
|
||||
DNS servers are not responding.
|
||||
|
||||
### Deprecated blocked services APIs
|
||||
|
||||
* The `GET /control/blocked_services/list` HTTP API; use the new `GET
|
||||
/control/blocked_services/get` API instead.
|
||||
|
||||
* The `POST /control/blocked_services/set` HTTP API; use the new `PUT
|
||||
/control/blocked_services/update` API instead.
|
||||
|
||||
### New blocked services APIs
|
||||
|
||||
* The new `GET /control/blocked_services/get` HTTP API.
|
||||
|
||||
* The new `PUT /control/blocked_services/update` HTTP API allows config
|
||||
updates.
|
||||
|
||||
These APIs accept and return a JSON object with the following format:
|
||||
|
||||
```json
|
||||
{
|
||||
"schedule": {
|
||||
"time_zone": "Local",
|
||||
"sun": {
|
||||
"start": 46800000,
|
||||
"end": 82800000
|
||||
}
|
||||
},
|
||||
"ids": [
|
||||
"vk"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### `/control/clients` HTTP APIs
|
||||
|
||||
The following HTTP APIs have been changed:
|
||||
|
||||
* `GET /control/clients`;
|
||||
* `GET /control/clients/find?ip0=...&ip1=...&ip2=...`;
|
||||
* `POST /control/clients/add`;
|
||||
* `POST /control/clients/update`;
|
||||
|
||||
The new field `blocked_services_schedule` has been added to JSON objects. It
|
||||
has the following format:
|
||||
|
||||
```json
|
||||
{
|
||||
"time_zone": "Local",
|
||||
"sun": {
|
||||
"start": 0,
|
||||
"end": 86400000
|
||||
},
|
||||
"mon": {
|
||||
"start": 60000,
|
||||
"end": 82800000
|
||||
},
|
||||
"thu": {
|
||||
"start": 120000,
|
||||
"end": 79200000
|
||||
},
|
||||
"tue": {
|
||||
"start": 180000,
|
||||
"end": 75600000
|
||||
},
|
||||
"wed": {
|
||||
"start": 240000,
|
||||
"end": 72000000
|
||||
},
|
||||
"fri": {
|
||||
"start": 300000,
|
||||
"end": 68400000
|
||||
},
|
||||
"sat": {
|
||||
"start": 360000,
|
||||
"end": 64800000
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## v0.107.36: API changes
|
||||
|
||||
### The new fields `"top_upstreams_responses"` and `"top_upstreams_avg_time"` in `Stats` object
|
||||
|
||||
* The new field `"top_upstreams_responses"` in `GET /control/stats` method
|
||||
shows the total number of responses from each upstream.
|
||||
|
||||
* The new field `"top_upstrems_avg_time"` in `GET /control/stats` method shows
|
||||
the average processing time in seconds of requests from each upstream.
|
||||
|
||||
## v0.107.30: API changes
|
||||
|
||||
### `POST /control/version.json` and `GET /control/dhcp/interfaces` content type
|
||||
@@ -19,8 +120,14 @@
|
||||
|
||||
```json
|
||||
{
|
||||
"target": {"domain":"example.com","answer":"answer-to-update"},
|
||||
"update": {"domain":"example.com","answer":"new-answer"}
|
||||
"target": {
|
||||
"domain": "example.com",
|
||||
"answer": "answer-to-update"
|
||||
},
|
||||
"update": {
|
||||
"domain": "example.com",
|
||||
"answer": "new-answer"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
@@ -78,7 +185,9 @@ return a JSON object with the following format:
|
||||
{
|
||||
"enabled": true,
|
||||
"interval": 3600,
|
||||
"ignored": ["example.com"],
|
||||
"ignored": [
|
||||
"example.com"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -109,7 +218,9 @@ accept and return a JSON object with the following format:
|
||||
"enabled": true,
|
||||
"anonymize_client_ip": false,
|
||||
"interval": 3600,
|
||||
"ignored": ["example.com"],
|
||||
"ignored": [
|
||||
"example.com"
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -241,7 +352,7 @@ JSON object with the following format:
|
||||
|
||||
```json
|
||||
{
|
||||
"name":"user name",
|
||||
"name": "user name",
|
||||
"language": "en",
|
||||
"theme": "auto"
|
||||
}
|
||||
@@ -317,8 +428,7 @@ the filters must be presented in a JSON object with the following format:
|
||||
|
||||
```json
|
||||
{
|
||||
"rules":
|
||||
[
|
||||
"rules": [
|
||||
"||example.com^",
|
||||
"# comment",
|
||||
"@@||www.example.com^"
|
||||
|
||||
Reference in New Issue
Block a user