Skip to content

feat: implement rate limiting on express server to prevent abuse - #421

Open
Johnsource-hub wants to merge 1 commit into
Abdulazeem-code:mainfrom
Johnsource-hub:feat/rate-limit-headers
Open

feat: implement rate limiting on express server to prevent abuse#421
Johnsource-hub wants to merge 1 commit into
Abdulazeem-code:mainfrom
Johnsource-hub:feat/rate-limit-headers

Conversation

@Johnsource-hub

Copy link
Copy Markdown

#closes
#381

Done. Branch feat/rate-limit-headers is ready with all 7 tests passing.
Changes:

  • stellar-payment-platform/server.js — Added express-rate-limit middleware (100 req/15 min) with legacyHeaders: true to expose X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers on every response.
  • stellar-payment-platform/tests/rate-limit.test.js — 7 tests covering header presence, values, decrement behavior, 429 responses, and header persistence on 429s.

@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

@renoschubert is attempting to deploy a commit to the Abdulazeem's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Jul 28, 2026

Copy link
Copy Markdown

@Johnsource-hub Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@Abdulazeem-code

Copy link
Copy Markdown
Owner

Please resolve conflicts

@Abdulazeem-code

Copy link
Copy Markdown
Owner

please resolve all the conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants