2019-06-06 10:57:40 +08:00
|
|
|
|
[English](limit-req.md)
|
2019-07-14 09:32:22 +08:00
|
|
|
|
# limit-req
|
2019-06-06 10:57:40 +08:00
|
|
|
|
|
|
|
|
|
限制请求速度的插件,使用的是漏桶算法。
|
|
|
|
|
|
|
|
|
|
### 参数
|
|
|
|
|
* `rate`:指定的请求速率(以秒为单位),请求速率超过 `rate` 但没有超过 (`rate` + `brust`)的请求会被加上延时
|
|
|
|
|
* `burst`:请求速率超过 (`rate` + `brust`)的请求会被直接拒绝
|
2019-06-13 14:39:35 +08:00
|
|
|
|
* `rejected_code`:当请求超过阈值被拒绝时,返回的 HTTP 状态码
|
2019-08-27 18:29:42 +08:00
|
|
|
|
* `key`:是用来做请求计数的依据,当前接受的 key 有:"remote_addr"(客户端IP地址), "server_addr"(服务端 IP 地址), 请求头中的"X-Forwarded-For" 或 "X-Real-IP"。
|
2019-06-06 10:57:40 +08:00
|
|
|
|
|
|
|
|
|
### 示例
|
|
|
|
|
|
|
|
|
|
#### 开启插件
|
|
|
|
|
下面是一个示例,在指定的 route 上开启了 limit req 插件:
|
|
|
|
|
|
|
|
|
|
```shell
|
2019-06-18 09:40:00 +08:00
|
|
|
|
curl http://127.0.0.1:9080/apisix/admin/routes/1 -X PUT -d '
|
2019-06-06 10:57:40 +08:00
|
|
|
|
{
|
2019-09-03 13:53:41 +08:00
|
|
|
|
"methods": ["GET"],
|
|
|
|
|
"uri": "/index.html",
|
|
|
|
|
"plugins": {
|
|
|
|
|
"limit-req": {
|
|
|
|
|
"rate": 1,
|
|
|
|
|
"burst": 2,
|
|
|
|
|
"rejected_code": 503,
|
|
|
|
|
"key": "remote_addr"
|
|
|
|
|
}
|
|
|
|
|
},
|
|
|
|
|
"upstream": {
|
|
|
|
|
"type": "roundrobin",
|
|
|
|
|
"nodes": {
|
|
|
|
|
"39.97.63.215:80": 1
|
|
|
|
|
}
|
|
|
|
|
}
|
2019-06-06 10:57:40 +08:00
|
|
|
|
}'
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
#### 测试插件
|
|
|
|
|
上述配置限制了每秒请求速率为 1,大于 1 小于 3 的会被加上延时,速率超过 3 就会被拒绝:
|
|
|
|
|
```shell
|
|
|
|
|
curl -i http://127.0.0.1:9080/index.html
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
当你超过,就会收到包含 503 返回码的响应头:
|
|
|
|
|
```
|
|
|
|
|
HTTP/1.1 503 Service Temporarily Unavailable
|
|
|
|
|
Content-Type: text/html
|
|
|
|
|
Content-Length: 194
|
|
|
|
|
Connection: keep-alive
|
|
|
|
|
Server: APISIX web server
|
|
|
|
|
|
|
|
|
|
<html>
|
|
|
|
|
<head><title>503 Service Temporarily Unavailable</title></head>
|
|
|
|
|
<body>
|
|
|
|
|
<center><h1>503 Service Temporarily Unavailable</h1></center>
|
|
|
|
|
<hr><center>openresty</center>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
这就表示 limit req 插件生效了。
|
|
|
|
|
|
|
|
|
|
#### 移除插件
|
|
|
|
|
当你想去掉 limit req 插件的时候,很简单,在插件的配置中把对应的 json 配置删除即可,无须重启服务,即刻生效:
|
|
|
|
|
|
|
|
|
|
```shell
|
2019-06-18 09:40:00 +08:00
|
|
|
|
curl http://127.0.0.1:9080/apisix/admin/routes/1 -X PUT -d '
|
2019-06-06 10:57:40 +08:00
|
|
|
|
{
|
2019-09-03 13:53:41 +08:00
|
|
|
|
"methods": ["GET"],
|
|
|
|
|
"uri": "/index.html",
|
|
|
|
|
"upstream": {
|
|
|
|
|
"type": "roundrobin",
|
|
|
|
|
"nodes": {
|
|
|
|
|
"39.97.63.215:80": 1
|
|
|
|
|
}
|
|
|
|
|
}
|
2019-06-06 10:57:40 +08:00
|
|
|
|
}'
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
现在就已经移除了 limit req 插件了。其他插件的开启和移除也是同样的方法。
|