Skip to main content
Version: 2.5




limit request rate using the "leaky bucket" method.


rateintegerrequiredrate > 0the specified request rate (number per second) threshold. Requests exceeding this rate (and below burst) will get delayed to conform to the rate.
burstintegerrequiredburst >= 0the number of excessive requests per second allowed to be delayed. Requests exceeding this hard limit will get rejected immediately.
keystringrequired["remote_addr", "server_addr", "http_x_real_ip", "http_x_forwarded_for", "consumer_name"]the user specified key to limit the rate, now accept those as key: "remote_addr"(client's IP), "server_addr"(server's IP), "X-Forwarded-For/X-Real-IP" in request header, "consumer_name"(consumer's username).
rejected_codeintegeroptional503[200,...,599]The HTTP status code returned when the request exceeds the threshold is rejected.

Key can be customized by the user, only need to modify a line of code of the plug-in to complete. It is a security consideration that is not open in the plugin.


How to enable on the route or serivce#

Take route as an example (the use of service is the same method), enable the limit-req plugin on the specified route.

curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -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": {            "": 1        }    }}'

You can open dashboard with a browser:, to complete the above operation through the web interface, first add a route:

add route

Then add limit-req plugin:

add plugin

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

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

HTTP/1.1 503 Service Temporarily UnavailableContent-Type: text/htmlContent-Length: 194Connection: keep-aliveServer: 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.

How to enable on the consumer#

To enable the limit-req plugin on the consumer, it needs to be used together with the authorization plugin. Here, the key-auth authorization plugin is taken as an example.

  1. Bind the limit-req plugin to the consumer
curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "username": "consumer_jack",    "plugins": {        "key-auth": {            "key": "auth-jack"        },        "limit-req": {            "rate": 1,            "burst": 1,            "rejected_code": 403,            "key": "consumer_name"        }    }}'
  1. Create a route and enable the key-auth plugin
curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "methods": ["GET"],    "uri": "/index.html",    "plugins": {        "key-auth": {            "key": "auth-jack"        }    },    "upstream": {        "type": "roundrobin",        "nodes": {            "": 1        }    }}'

Test Plugin

The value of rate + burst is not exceeded.

curl -i -H 'apikey: auth-jack'HTTP/1.1 200 OK......

When the value of rate + burst is exceeded.

curl -i -H 'apikey: auth-jack'HTTP/1.1 403 Forbidden.....<html><head><title>403 Forbidden</title></head><body><center><h1>403 Forbidden</h1></center><hr><center>openresty</center></body></html>

Explains that the limit-req plugin tied to consumer has taken 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 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "methods": ["GET"],    "uri": "/index.html",    "id": 1,    "plugins": {    },    "upstream": {        "type": "roundrobin",        "nodes": {            "": 1        }    }}'

Remove the limit-req plugin on consumer.

curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "username": "consumer_jack",    "plugins": {        "key-auth": {            "key": "auth-jack"        }    }}'

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