Task 2: The "Placebo" Rate Limiter
Problem
The server includes a rate limiting mechanism, but it does not actually block excessive or abusive traffic.
Requests beyond the allowed threshold continue to pass through as if no limiter exists.
Points: 60
Steps to Reproduce
- Start the server
- Send rapid consecutive requests (via script or load-testing tool)
- Observe the rate limiter’s supposed threshold
- Notice: Requests are never blocked or throttled, even when limits are exceeded
Expected Behavior
The rate limiter should:
- Track requests per IP or client
- Enforce defined limits (e.g., X requests per minute)
- Block or throttle clients exceeding the threshold
- Return proper HTTP error codes (e.g., 429 Too Many Requests)
Submission Guidelines
- Comment on this issue with your proposed solution approach
- Wait for issue assignment from reviewers
- Create a PR with clear commit messages
- Reference this issue in your PR description
Task 2: The "Placebo" Rate Limiter
Problem
The server includes a rate limiting mechanism, but it does not actually block excessive or abusive traffic.
Requests beyond the allowed threshold continue to pass through as if no limiter exists.
Points: 60
Steps to Reproduce
Expected Behavior
The rate limiter should:
Submission Guidelines