issuer.Cache: the certificate cache behind the Issuer seam #46
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
mikluko/multiproxy!46
Loading…
Reference in a new issue
No description provided.
Delete branch "refactor/issuer-cache"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Candidate 4 of the architecture review.
Caching, per-name locking and expiry lived in the MITM handler, tested only through a full
CONNECTsession.issuer.Cacheis now a second adapter at the Issuer seam: it keeps the certificates another Issuer issues, per common name, and issues again pastNotAfter. Concurrent requests for one name wait for a single issue, and errors are not kept.TestCachecovers each point without TLS or a proxy.MITMHandlerkeeps only the mapping from host to certificate names. Its default Issuer and the command's both wrapSelfSignedCAin the cache.Breaking for library users:
MITMHandler.CertCacheSizeis removed. An Issuer you set yourself is called on everyCONNECTunless you wrap it inissuer.Cache.The suite passes three times in a row under
-race.