limit-req

limit request rate using the “leaky bucket” method.

Parameters

rate: is the specified request rate (number per second) threshold.Requests exceeding this rate (and below burst) will get delayed to conform to the rate.
burst: is the number of excessive requests per second allowed to be delayed. Requests exceeding this hard limit will get rejected immediately.
rejected_code: The HTTP status code returned when the request exceeds the threshold is rejected. The default is 503.
key: is the user specified key to limit the rate, now only accept “remote_addr”(client's IP) as key

example

enable plugin

Here's an example, enable the limit req plugin on the specified route:

curl http://127.0.0.1:9080/apisix/admin/routes/1 -X PUT -d '
{
	"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
		}
	}
}'

test plugin

The above configuration limits the request rate to 1 per second. If it is greater than 1 and less than 3, the delay will be added. If the rate exceeds 3, it will be rejected:

curl -i http://127.0.0.1:9080/index.html

When you exceed, you will receive a response header with a 503 return code:

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>

This means that the limit req plugin is in effect.

disable plugin

When you want to disable the limit req plugin, it is very simple, you can delete the corresponding json configuration in the plugin configuration, no need to restart the service, it will take effect immediately:

curl http://127.0.0.1:9080/apisix/admin/routes/1 -X PUT -d '
{
	"methods": ["GET"],
	"uri": "/index.html",
	"id": 1,
	"plugins": {
	},
	"upstream": {
		"type": "roundrobin",
		"nodes": {
			"39.97.63.215:80": 1
		}
	}
}'

The limit req plugin has been disabled now. It works for other plugins.