Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add delay after HTTP 429 Too Many Requests

Open
  • Is something wrong?
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli, networking

Research direction

No file, test, or configuration entry point is named. Start by locating the HTTP retry handling and existing website configuration, then determine how a delay could be represented globally or per website. Done means HTTP 429 responses wait for the configured delay before retrying, with the per-website behavior clarified.

Written by the indexing model from the issue text.

Description

enhancement

Add a configurable delay to wait before retrying for websites that return 429s. Ideally would be per website.

Dominant language
Ruby
Stars
5
Forks
1
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dblock/ruby-link-checker

All issues in dblock/ruby-link-checker

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.