Fix Jellyfin CORS #765
Merged
Fix Jellyfin CORS #765
+11
−5
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
github-project-automation
bot
moved this from PRs
to PRs Approved
in Issue & PR Tracker
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This MR change the CORS for jellyfin, modifying it only in case of WebOS.
closes #754
Benefits of this PR and context
I misunderstood a comment on a previous MR from @quietsy on this subject. It introduced bugs on Chromecast and in
add_headerfromssl.confon jellyfin nginx templates configs.How Has This Been Tested?
Tested the subdomain configuration on
I don't own a Chromecast. @Zazcallabah could you test it on your own device?
Source / References