Skip to content
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

[Relay White Noise Error] Correct Mapping of Rate-Limiting Errors (429 Handling) #3444

Open
quiet-node opened this issue Feb 3, 2025 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@quiet-node
Copy link
Member

Problem

Currently, the Relay incorrectly maps 429 Too Many Requests responses from the Mirror Node to 409 Conflict before returning them to clients. This misalignment causes:

  • Clients being unaware of rate limits, potentially leading to excessive retries.
  • A lack of clarity regarding whether failures are due to conflicts or rate limits.
  • Potential inconsistencies in error handling across different RPC endpoints.

Solution

  • Ensuring that 429 Too Many Requests from the Mirror Node is correctly returned as 429 to clients.
  • Maintaining consistency in how rate-limiting responses are handled across different endpoints.
  • Improving client awareness of rate limits, reducing unnecessary load on the Relay and Mirror Node.

Alternatives

No response

@quiet-node quiet-node added the enhancement New feature or request label Feb 3, 2025
@quiet-node quiet-node added this to the 0.67.0 milestone Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant