-
-
Notifications
You must be signed in to change notification settings - Fork 0
Add public middleware with basic rate limiting and timestamp checks #87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Warning Rate limit exceeded@gocanto has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 21 minutes and 57 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (5)
WalkthroughAdds a new PublicMiddleware for public endpoints with request header validation, IP extraction, rate limiting, timestamp validation, and replay protection via TTL cache. Includes constructor with defaults, dependency guard, and unit tests covering missing/expired timestamps, replay detection, and rate limiting. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant C as Client
participant PM as PublicMiddleware
participant RL as RateLimiter
participant TS as Timestamp Validator
participant RC as TTL Cache
participant H as Next Handler
C->>PM: HTTP request (X-Request-ID, X-API-Timestamp, X-Forwarded-For)
PM->>PM: guardDependencies()
alt Missing headers / invalid IP
PM-->>C: 401 UnauthenticatedError
else Dependencies OK
PM->>RL: Check IP quota
alt Rate limit exceeded
RL-->>PM: TooMany
PM-->>C: 429 Too Many Requests
else Within quota
PM->>TS: Validate timestamp (clockSkew, disallowFuture)
alt Invalid/expired timestamp
TS-->>PM: Invalid
PM-->>C: 401 UnauthenticatedError
else Timestamp valid
PM->>RC: Check/set (IP + RequestID) within requestTTL
alt Duplicate found
RC-->>PM: Duplicate
PM->>RL: Increment IP usage
PM-->>C: 401 UnauthenticatedError (replay)
else New request
RC-->>PM: Stored
PM->>H: Call next handler
H-->>PM: Response
PM-->>C: Response
end
end
end
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @gocanto, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces a new PublicMiddleware component designed to enhance the security and stability of public API endpoints. It implements essential protections such as IP-based rate limiting and timestamp validation to prevent common attack vectors like replay attacks, ensuring that requests are legitimate and not excessively frequent.
Highlights
- New Public Middleware: Introduces PublicMiddleware to provide basic security for public endpoints, including IP-based rate limiting and timestamp validation.
- Replay Attack Prevention: Implements a mechanism using TTLCache to block replayed requests by checking for duplicate request IDs within a defined time-to-live window.
- Comprehensive Testing: Adds a dedicated test file (public_middleware_test.go) with tests covering invalid headers, expired timestamps, and the rate limiting and replay prevention functionalities.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a PublicMiddleware to provide rate limiting and replay attack protection for public endpoints. The implementation is clean and uses a TTLCache for checking request nonces and an in-memory rate limiter. The tests cover the main success and failure paths, including rate limiting after a replayed request. My review includes a suggestion to correct an error status code for server-side configuration issues and a recommendation to expand test coverage for invalid request headers using a table-driven approach.
Summary
Testing
go test ./pkg/middleware -count=1https://chatgpt.com/codex/tasks/task_e_68be7b7819608333a4c727b82c5b3f1e
Summary by CodeRabbit