rateLimit for each path has a common counter about elysia-rate-limit

[rayriffy]

This is not a bug. By default rateLimit context will be applied globally and disregarding any hierarchy, use scoping option to make plugin affect per routes.

[doroved]

This is not a bug. By default rateLimit context will be applied globally and disregarding any hierarchy, use scoping option to make plugin affect per routes.

scope has nothing to do with it. You need to add url.pathname to the key in the generator
Maybe it's better to make it by default, so you don't have to specify it every time.
Otherwise now, if you exhaust the limit on one router you will be blocked everywhere!

That's how it should be.

    generator: (req) => {
      const path = new URL(req.url).pathname
      const ip = req.headers.get('x-real-ip')

      const res = ip !== null ? ip : 'anonymous'
      return res + path
    },

You were clearly in a hurry to close the issue.

[rayriffy]

scoping is meant to separate rate limit per instances to grouping by each categories, by design rate limit should be counted globally this is also a default behavior for fastify, and express as well. If you want per api route you should create your own generator that's what it's designed for. this project should not cover every tiny cases otherwise it will be extremely bloated

and do not make an accusation like that to anyone EVER