title | keywords | description | |||
---|---|---|---|---|---|
uri-blocker |
|
This document contains information about the Apache APISIX uri-blocker Plugin. |
The uri-blocker
Plugin intercepts user requests with a set of block_rules
.
Name | Type | Required | Default | Valid values | Description |
---|---|---|---|---|---|
block_rules | array[string] | True | List of regex filter rules. If the request URI hits any one of the rules, the response code is set to the rejected_code and the user request is terminated. For example, ["root.exe", "root.m+"] . |
||
rejected_code | integer | False | 403 | [200, ...] | HTTP status code returned when the request URI hits any of the block_rules . |
rejected_msg | string | False | non-empty | HTTP response body returned when the request URI hits any of the block_rules . |
|
case_insensitive | boolean | False | false | When set to true , ignores the case when matching request URI. |
The example below enables the uri-blocker
Plugin on a specific Route:
:::note
You can fetch the admin_key
from config.yaml
and save to an environment variable with the following command:
admin_key=$(yq '.deployment.admin.admin_key[0].key' conf/config.yaml | sed 's/"//g')
:::
curl -i http://127.0.0.1:9180/apisix/admin/routes/1 -H "X-API-KEY: $admin_key" -X PUT -d '
{
"uri": "/*",
"plugins": {
"uri-blocker": {
"block_rules": ["root.exe", "root.m+"]
}
},
"upstream": {
"type": "roundrobin",
"nodes": {
"127.0.0.1:1980": 1
}
}
}'
Once you have configured the Plugin as shown above, you can try accessing the file:
curl -i http://127.0.0.1:9080/root.exe?a=a
HTTP/1.1 403 Forbidden
Date: Wed, 17 Jun 2020 13:55:41 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 150
Connection: keep-alive
Server: APISIX web server
... ...
You can also set a rejected_msg
and it will be added to the response body:
HTTP/1.1 403 Forbidden
Date: Wed, 17 Jun 2020 13:55:41 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 150
Connection: keep-alive
Server: APISIX web server
{"error_msg":"access is not allowed"}
To remove the uri-blocker
Plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect.
curl http://127.0.0.1:9180/apisix/admin/routes/1 -H "X-API-KEY: $admin_key" -X PUT -d '
{
"uri": "/*",
"upstream": {
"type": "roundrobin",
"nodes": {
"127.0.0.1:1980": 1
}
}
}'