Fix Jellyfin to use path-specific scanning instead of full library refresh #7
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.
Summary
This PR fixes two issues with Jellyfin integration:
Path-specific scanning:
JellyfinServer.scan_path()was ignoring thepathparameter and calling/Library/Refresh, which triggers a full scan of ALL libraries. Now uses/Library/Media/Updatedto only refresh the library containing the specified path.Modern authentication: Updates from legacy
X-MediaBrowser-Tokenheader to modernAuthorization: MediaBrowser Token="..."format, which is required whenEnableLegacyAuthorizationis disabled (the default in modern Jellyfin).Changes
/Library/Media/Updatedendpoint with properMediaUpdateInfoDtopayloadAuthorization: MediaBrowser Token="..."header formatJellyfinServer.scan_path(),MediaServerScanner._scan_jellyfin(), and test connection endpointTest plan
EnableLegacyAuthorization=false(default)Supersedes #6 (auth fix is included in this PR)