Rate limit middleware doesn't set headers or provide metadata via interface.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32.7k
- Forks
- 2.7k
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 6
Description
Similar rate limit middleware like https://github.com/go-chi/httprate handles automatically setting appropriate X-Rate-Limit-* and Retry-After headers on a rate limit event which this middleware does not. This is compounded by the RateLimiterStore interface not providing a mechanism for returning metadata to set them manually either.
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.
Research direction
Start by locating the rate limit middleware and the RateLimiterStore interface, then compare their behavior with the linked go-chi/httprate implementation. Define the metadata and header behavior needed for rate-limit events, and verify that the middleware or store interface exposes it and that the relevant tests cover the resulting X-Rate-Limit-* and Retry-After headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100