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

feat: implement rate limiting #38

Merged
merged 1 commit into from
Oct 11, 2023
Merged

feat: implement rate limiting #38

merged 1 commit into from
Oct 11, 2023

Conversation

matusf
Copy link
Owner

@matusf matusf commented Oct 10, 2023

When 429 (Too Many Requests) or 503 (Service unavailable) status codes are received, the fuzzer will try to resend the request after number of seconds specified in Retry-After header. If the header is not present it will use exponential backoff algorithm with a start value of 1 second.

Closes: #23

@matusf matusf marked this pull request as ready for review October 11, 2023 13:12
When 429 (Too Many Requests) or 503 (Service unavailable) status codes
are received, the fuzzer will try to resend the request after number of
seconds specified in `Retry-After` header. If the header is not present
it will use exponential backoff algorithm with a start value of 1
second.

If it won't succeed after `max_backoff` tries, it will abort fuzzing
current endpoint.

Closes: #23
@matusf matusf changed the title feat: implement exponential backoff feat: implement rate limiting Oct 11, 2023
@matusf matusf merged commit 60f13e0 into master Oct 11, 2023
3 checks passed
@matusf matusf deleted the feat/rate-limiting branch October 16, 2023 16:54
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.

Add a rate-limiting feature for APIs w/ rate-limits
1 participant