spring-cloud / spring-cloud/spring-cloud-gateway
Allow users to specify the redis key via a strategy of some kind
Open
Nobody has claimed this yet.
enhancement
in: server-webflux
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Previously, there was a bug that leaked rate limiter keys across routes #2288
#2517 added the routeId to that key, but that may not be ideal in all situations.
See https://github.com/spring-cloud/spring-cloud-gateway/pull/2517#issuecomment-2657176323
Contributor guide
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.
Research direction
Start by reading issue #2288 and pull request #2517, especially the linked discussion about adding routeId to rate-limiter keys. Trace how the current key is formed and define the strategy's expected behavior for routes; done means users can choose the Redis key without reintroducing key leakage across routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis, spring, spring-boot
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100