letsencrypt / letsencrypt/pebble
Return 429 and 503 occasionally
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
The Let's Encrypt API (overall, through a combination of Boulder and the load balancers) returns code 503 when the servers are overloaded, and code 429 when a given client is retrying too often, both with a Retry-After header.
Pebble should return those codes occasionally, too.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing Pebble's ACME request handling and existing error-response tests, then determine how occasional 429 and 503 responses with Retry-After should be exercised; done means both responses are covered by repeatable tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100