+ GET /filtering/check_host: Check if host name is filtered
This commit is contained in:
@@ -56,6 +56,7 @@ Contents:
|
||||
* API: Get filtering parameters
|
||||
* API: Set filtering parameters
|
||||
* API: Set URL parameters
|
||||
* API: Domain Check
|
||||
* Log-in page
|
||||
* API: Log in
|
||||
* API: Log out
|
||||
@@ -1355,6 +1356,30 @@ Response:
|
||||
200 OK
|
||||
|
||||
|
||||
### API: Domain Check
|
||||
|
||||
Check if host name is filtered.
|
||||
|
||||
Request:
|
||||
|
||||
GET /control/filtering/check_host?name=hostname
|
||||
|
||||
Response:
|
||||
|
||||
200 OK
|
||||
|
||||
{
|
||||
"reason":"FilteredBlackList",
|
||||
"filter_id":1,
|
||||
"rule":"||doubleclick.net^",
|
||||
"service_name": "...", // set if reason=FilteredBlockedService
|
||||
|
||||
// if reason=ReasonRewrite:
|
||||
"cname": "...",
|
||||
"ip_addrs": ["1.2.3.4", ...],
|
||||
}
|
||||
|
||||
|
||||
## Log-in page
|
||||
|
||||
After user completes the steps of installation wizard, he must log in into dashboard using his name and password. After user successfully logs in, he gets the Cookie which allows the server to authenticate him next time without password. After the Cookie is expired, user needs to perform log-in operation again.
|
||||
|
||||
Reference in New Issue
Block a user