Document backend rate limit behavior#483
Open
chrisx9z wants to merge 1 commit into
Open
Conversation
|
@chrisx9z is attempting to deploy a commit to the Edeh Victor's projects Team on Vercel. A member of the Team first needs to authorize it. |
This commit documents rate-limited backend endpoints, expected 429 responses, and frontend retry guidance for clients.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Closes #466.
Adds backend rate-limit documentation to
docs/backend_testing.md.The new section covers:
429behaviorVerification
rg -n "relayerLimiter|fee-bump|exportLimiter|docsLimiter|metricsRateLimit" server/srcrg -n "3 requests per 15 minutes|5 requests per 15 minutes|60 requests per 15 minutes|10 requests per minute|429|exponential backoff" docs/backend_testing.mdCommit comment
This commit documents rate-limited backend endpoints, expected 429 responses, and frontend retry guidance for clients.