Skip to content

Back-off mechanic for rate limiting sites #23

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.

Sign up for GitHub

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

Jump to bottom
Closed
AuHau opened this issue Jun 29, 2021 · 1 comment · Fixed by AuHau/link-checker#2 · May be fixed by #26
Closed

Back-off mechanic for rate limiting sites #23

AuHau opened this issue Jun 29, 2021 · 1 comment · Fixed by AuHau/link-checker#2 · May be fixed by #26

Comments

@AuHau
Copy link

AuHau commented Jun 29, 2021

GitHub for example uses rate limiting when hitting his infrastructure which leads to lot of requests failing with Too Many Requests (code 429) , so I would propose to implement back off mechanism that would on one hand slow down the execution but would respect not DoS the services.
@AuHau
Copy link
Author

AuHau commented Jun 29, 2021

Although I guess HTTP caching might help a lot to mitigate this problem 🤔

This was referenced Jul 1, 2021
Open
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci: update nodejs versions AuHau/link-checker
feat: rate limitting AuHau/link-checker
1 participant
@AuHau