[Improvement]: Advanced Rate Limit Policy improvements
@Saadha123 is already working on this.
Since Sep 3, 2026.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
Problem
Currently, advanced-ratelimit's keyExtraction can only read from headers or properties present on the original request. This means a key set by an earlier policy in the chain
can't be used to selectively apply throttling — there's no way to say "only throttle traffic matching a specific value on a specific resource path," everything reaching a quota
gets bucketed and counted.
A common use case this blocks: applying a rate limit only for a specific client/application on a specific route, while leaving all other traffic on that route completely
unaffected.
Possible Solutions
Provide the option to define a key and a filter to reduce scope — for example, a regex to select which values a quota should apply to:
keyExtraction:
- type: header
key: x-app-id
filter: 'guest-*|channel-partner'Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.