Fix #11: Bounty Claim: Gateway rate limiting middleware ($65) - #27
Open
Nexussyn wants to merge 3 commits into
Open
Fix #11: Bounty Claim: Gateway rate limiting middleware ($65)#27Nexussyn wants to merge 3 commits into
Nexussyn wants to merge 3 commits into
Conversation
…ay rate limiting middleware ($65)
…ay rate limiting middleware ($65)
…ay rate limiting middleware ($65)
Author
Automated SubmissionThis PR addresses issue #11. Summary: Implemented a sliding window rate limiter middleware for the market gateway with configurable limits via environment variables, proper HTTP 429 responses with standard rate limit headers, and comprehensive test coverage. Please review the changes. If adjustments are needed, comment here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #11
Summary
Implemented a sliding window rate limiter middleware for the market gateway with configurable limits via environment variables, proper HTTP 429 responses with standard rate limit headers, and comprehensive test coverage.
Changes
Gateway Rate Limiting Middleware
Summary
Implements a sliding window rate limiter for the market gateway to protect against traffic abuse and ensure fair resource allocation across clients.
Changes Made
market/gateway/middleware.go: Core rate limiting implementationMARKET_RATE_LIMIT_PER_MINUTE- requests allowed per minute (default: 120)MARKET_RATE_LIMIT_BURST- burst allowance (default: 10)market/gateway/middleware_test.go: Comprehensive test coverageTestRateLimitAllowedTraffic- verifies normal requests pass throughTestRateLimitBlockedTraffic- verifies 429 response when limit exceededTestRateLimitEnvOverride- verifies environment variable configurationTestRateLimitPerIPIsolation- verifies per-IP tracking isolationmarket/gateway/api.go: Cleaned up unused imports and integrated middlewareResponse Headers
X-RateLimit-LimitX-RateLimit-RemainingRetry-After