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.
Description
This PR implements API rate limiting to strengthen the system’s security and prevent abuse.
It introduces a middleware that restricts the number of requests a user can make within a defined time window.
Stricter limits are applied to sensitive authentication endpoints to mitigate brute-force attacks.
Semver Changes
Issues
Closes #18 — [Feature]: Add API Rate Limiting
Checklist
🧩 Summary
/api/auth/login
and/api/auth/register
.429 Too Many Requests
when the limit is exceeded.🧪 How to Test
/api/auth/login
and/api/auth/register
.429 Too Many Requests
.Labels:
security
·enhancement
·middleware
Related PR: #25