kenzuya/unshackle
1
0
Fork 2
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-11-14 13:05:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(vaults): stop querying sibling KIDs and skip unavailable vaults

Browse Source 
The server CDM stub names only the manifest's KIDs; sibling keys stay content keys. API and HTTP vaults retry a 429, and a vault that is down or still rate limited costs one timeout per run.
This commit is contained in:
imSp4rky
2026-10-16 14:49:37 -06:00
parent ecb8296de8
commit dc169f81e1
10 changed files with 261 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/configuration/vaults.md
+6
View File
@@ -56,3 +56,9 @@ key_vaults:
Timeout in seconds for vault operations. Injected automatically into any backend whose
constructor accepts a `timeout` parameter (a per-vault `timeout` still wins). The `MySQL` backend
uses it as the default `connect_timeout`.
The `API` and `HTTP` backends send a request again up to 3 times when the vault answers
`429 Too Many Requests`. They wait the `Retry-After` time, but never longer than this timeout.
A connection failure or a timeout is not tried again. The run does not use a vault again after a
connection failure, a timeout, or a `429` that continues after the retries, so a vault that is
down costs one timeout per run.