letsencrypt / letsencrypt/boulder
Permit caching of /directory
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Currently, requesting the /directory gives this response header:
cache-control: public, max-age=0, no-cache
A strictly implemented client is forced not to cache the result, but fetch a new copy of the directory every time it is needed. However, the contents of the directory are likely to change very rarely.
Boulder should instead set a reasonable expires header, to reduce unnecessary requests.
This would also help to reduce log volume, see issue #3050. 😉
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
Start by locating the /directory endpoint and inspect how its response headers are set. Determine a reasonable expiration policy, then verify that the response permits caching and that the behavior addresses the unnecessary requests described in this issue; issue #3050 provides related context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100