onLimitReached , or running custom code about express-slow-down HOT 5 CLOSED

Oof, I'm sorry, I didn't think about that.

Here's a couple of options that are both a little dumb, but might be good enough:

1. Add a custom middleware that runs after express-slow-down and checks req.slowDown:

   app.use(slowDown({
       // ...
   }));
   app.use((req, res, next) => {
       if (request.slowDown.current === request.slowDown.limit + 1) {
           // onLimitReached code here
       }
       next();
   }));

   The gotcha with this approach is that it now fires after the delay, whereas onLimitReached fired before the delay. That might be acceptable for logging purposes, though.

2. Drop express-slow-down, and instead use express-rate-limit with a custom handler as shown in the docs. However, make the custom handler slow down responses instead of blocking them:

   app.use(rateLimit({
       // ...
       max: 1, // previous delayAfter value here
       handler: (request, response, next, options) => {
           if (request.rateLimit.used === request.rateLimit.limit + 1) {
               // onLimitReached code here
           }
           const delay = (request.used - request.limit) * 1000
           const timerId = setTimeout(next, delay)
           response.on('close', () => clearTimeout(timerId))
       },
   })

   (Basically recreate a simpler version of express-slow-down v2.0.0.)

from express-slow-down.

thanks, made do with a variation based on 1. Found a bug see #46.

from express-slow-down.