Enhance rate limiting by adding a skipper function for health checks #54
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.
This pull request introduces improvements to the server's rate limiting functionality, making it more flexible and allowing certain routes to be excluded from rate limiting. It also introduces a constant for the health check route path and ensures the health check endpoint is not rate limited.
Rate limiting enhancements:
RequestLimitSkipperoption to the server, allowing custom logic to skip rate limiting for specific requests. The main application now uses this to exempt the health check endpoint from rate limiting. [1] [2]Health check endpoint improvements:
HealthPathconstant ininternal/controllers/health.goand updated the route registration to use this constant, ensuring consistency and easier maintenance.HealthPathconstant when configuring the rate limit skipper.Dependency update:
echo/v4package import tomain.goto support the new skipper logic.