letsencrypt / letsencrypt/boulder
ccadb prober: cache CCADB results and ignore errors for up to 48 hours
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
The CCADB prober fetches from the CCADB as the source of truth for our CRL URLs, but we don't need the results to be super fresh. And if CCADB is down for a bit, we don't want the prober to fire. We should catch the last copy we successfully fetched, and ignore errors from CCADB so long as our copy of the data is less than 48 hours old.
Contributor guide
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
Locate the CCADB prober and trace its fetch and error-handling path. Determine where the last successful CCADB result can be retained, then verify that fresh results are used normally and CCADB errors are ignored only while the retained data is under 48 hours old.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100