letsencrypt / letsencrypt/pebble
Retry-After headers for polling orders and authorizations
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
Eventually, the server knows when it will retry a challenge validation etc. and therefore when it makes sense for the client to recheck the status.
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 files, tests, or entry points are named. Start by locating the polling handlers for orders and authorizations, then determine how challenge validation retry timing is represented. Done means those polling responses include Retry-After values indicating when the client should check again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100