Skip to content

Conversation

@Nabil-Salah
Copy link
Contributor

@Nabil-Salah Nabil-Salah commented Jul 8, 2025

Description

Describe the changes introduced by this PR and what does it affect

Changes

List of changes this PR includes

Related Issues

Checklist

  • Tests included
  • Build pass
  • Documentation
  • Code format and docstring

image

@Nabil-Salah Nabil-Salah force-pushed the development_proxy_ratelimiter branch from 3f1d504 to 7ec4aea Compare July 8, 2025 10:25
Copy link
Member

@sameh-farouk sameh-farouk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we first consider using our reverse-proxy rate limiter? Since it’s a simple IP-based limiter that doesn’t require any business logic, configuring it properly could reduce application complexity and is often more reliable than implementing custom rate-limiting code for such a common use case.

That said, I’m also wondering whether this has been tested behind a reverse proxy. The way GetClientIP parses headers may cause all users to be grouped under the same IP address (depending on how the reverse proxy is configured).

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.

3 participants