Repository navigation
Fix playlist ClearKey metadata compatibility - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three targeted compatibility fixes, preserving existing recorder behavior:
KID:KEYmetadata into individual keys in the shared discovery normalizer.|User-Agent=...&Referer=...&Origin=...headers on remote ClearKey license URLs and send them only to the license request (not stream or manifest requests).sonuxsJSON key array when older key fields are absent.Includes shared parser/JSON regression tests and isolated license-request tests with mocked network requests. No changes to unrelated recorder behavior or to
main.