fastify-rate-limit
A low overhead rate limiter for your routes. Supports Fastify 2.x
versions.
Please refer to this branch and related versions for Fastify 1.x compatibility.
Install
npm i fastify-rate-limit
Usage
Register the plugin pass to it some custom option.
This plugin will add an onRequest
hook to check if the clients (based on their ip) has done too many request in the given timeWindow.
const fastify = require('fastify')()
fastify.register(require('fastify-rate-limit'), {
max: 100,
timeWindow: '1 minute'
})
fastify.get('/', (req, reply) => {
reply.send({ hello: 'world' })
})
fastify.listen(3000, err => {
if (err) throw err
console.log('Server listening at http://localhost:3000')
})
In case a client reaches the maximum number of allowed requests, a standard Fastify error will be returned to the user with the status code setted to 429
:
{
statusCode: 429,
error: 'Too Many Requests',
message: 'Rate limit exceeded, retry in 1 minute'
}
You can change the response by providing a callback to errorResponseBuilder
.
The response will have some additional headers:
Header | Description |
---|
x-ratelimit-limit | how many request the client can do |
x-ratelimit-remaining | how many request remain to the client in the timewindow |
retry-after | if the max has been reached, the millisecond the client must wait before perform new requests |
Options
You can pass the following options during the plugin registration:
fastify.register(require('fastify-rate-limit'), {
global : false,
max: 3,
timeWindow: 5000,
cache: 10000,
whitelist: ['127.0.0.1'],
redis: new Redis({ host: '127.0.0.1' }),
skipOnError: true,
keyGenerator: function(req) { },
errorResponseBuilder: function(req, context) { },
})
global
: indicates if the plugin should apply the rate limit setting to all routes within the encapsulation scopemax
: is the maximum number of requests a single client can perform inside a timeWindow. It can be a sync function with the signature (req, key) => {}
where req
is the Fastify request object and key
is the value generated by the keyGenerator
. The function must return a number.timeWindow:
the duration of the time window. It can be expressed in milliseconds or as a string (in the ms
format)cache
: this plugin internally uses a lru cache to handle the clients, you can change the size of the cache with this optionwhitelist
: array of string of ips to exclude from rate limiting. It can be a sync function with the signature (req, key) => {}
where req
is the Fastify request object and key
is the value generated by the keyGenerator
. If the function return a truthy value, the request will be excluded from the rate limit.redis
: by default this plugins uses an in-memory store, which is fast but if you application works on more than one server it is useless, since the data is store locally.
You can pass a Redis client here and magically the issue is solved. To achieve the maximum speed, this plugins requires the use of ioredis
skipOnError
: if true
it will skip errors generated by the storage (eg, redis not reachable).keyGenerator
: a function to generate a unique identifier for each incoming request. Defaults to (req) => req.ip
, the IP is resolved by fastify using req.connection.remoteAddress
or req.headers['x-forwarded-for']
if trustProxy option is enabled. Use it if you want to override this behaviorerrorResponseBuilder
: a function to generate a custom response object. Defaults to (req, context) => ({statusCode: 429, error: 'Too Many Requests', message: ``Rate limit exceeded, retry in ${context.after}``})
keyGenerator
example usage:
fastify.register(require('fastify-rate-limit'), {
keyGenerator: function(req) {
return req.headers['x-real-ip']
|| req.headers['x-client-ip']
|| req.headers['x-forwarded-for']
|| req.session.username
|| req.raw.ip
})
Variable max
example usage:
fastify.register(rateLimit, {
keyGenerator (req) { return req.headers['service-key'] },
max: (req, key) => { return key === 'pro' ? 3 : 2 },
timeWindow: 1000
})
errorResponseBuilder
example usage:
fastify.register(require('fastify-rate-limit'), {
errorResponseBuilder: function(req, context) {
return {
code: 429,
error: 'Too Many Requests',
message: `I only allow ${context.max} requests per ${context.after} to this Website. Try again soon.`,
date: Date.now()
}
}
})
Dynamic whitelist
example usage:
fastify.register(require('fastify-rate-limit'), {
whitelist: function(req, key) {
return req.headers['x-app-client-id'] === 'internal-usage'
}
})
Options on the endpoint itself
Rate limiting can be configured also for some routes, applying the configuration independently.
For example the whitelist
if configured:
- on the plugin registration will affect all endpoints within the encapsulation scope
- on the route declaration will affect only the targeted endpoint
The global whitelist is configured when registering it with fastify.register(...)
.
The endpoint whitelist is set on the endpoint directly with the { config : { rateLimit : { whitelist : [] } } }
object.
ACL checking is performed based on the value of the key from the keyGenerator
.
In this example we are checking the IP address, but it could be a whitelist of specific user identifiers (like JWT or tokens):
const fastify = require('fastify')()
fastify.register(require('fastify-rate-limit'),
{
global : false,
max: 3000,
whitelist: ['192.168.0.10'],
redis: redis,
})
fastify.get('/', {
config: {
rateLimit: {
max: 3,
timeWindow: '1 minute'
}
}
}, (req, reply) => {
reply.send({ hello: 'from ... root' })
})
fastify.get('/private', {
config: {
rateLimit: {
max: 3,
timeWindow: '1 minute'
}
}
}, (req, reply) => {
reply.send({ hello: 'from ... private' })
})
fastify.get('/public', (req, reply) => {
reply.send({ hello: 'from ... public' })
})
fastify.get('/public/sub-rated-1', {
config: {
rateLimit: {
timeWindow: '1 minute',
whitelist: ['127.0.0.1'],
onExceeding: function (req) {
console.log('callback on exceededing ... executed before response to client')
},
onExceeded: function (req) {
console.log('callback on exceeded ... to black ip in security group for example, req is give as argument')
}
}
}
}, (req, reply) => {
reply.send({ hello: 'from sub-rated-1 ... using default max value ... ' })
})
In the route creation you can override the same settings of the plugin registration plus the additionals options:
onExceeding
: callback that will be executed each time a request is made to a route that is rate limitedonExceeded
: callback that will be executed when a user reached the maximum number of tries. Can be useful to blacklist clients
License
MIT
Copyright © 2018 Tomas Della Vedova