-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Toggles for qbittorrent's themepark "add-on" #184
Comments
Specifically this is about these two settings tweaks here:
|
saltydk
added a commit
that referenced
this issue
Feb 8, 2024
In the case of using theme.park you would probably just modify qbittorrent_themepark_headers: "\"content-security-policy: default-src 'self'; style-src 'self' 'unsafe-inline' theme-park.dev raw.githubusercontent.com use.fontawesome.com; img-src 'self' theme-park.dev raw.githubusercontent.com data:; script-src 'self' 'unsafe-inline'; object-src 'none'; form-action 'self'; frame-ancestors 'self'; font-src use.fontawesome.com;\"" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem
If using qbittorrent with themepark enabled with organizr, if you put it in iframe it won't work.
It's because the themepark role sets the
frame-ancestors self
custom HTTP header in qbit's option.Describe any solutions you think might work
I solved it by using this header:
(I'm unsure whether adding the internal address does something or not to be fair)
Using the config file or the inventory system we could set add additional domains to the "base" install of themepark within Qbit, like this maybe:
and Saltbox can add it alongside the original
self
The text was updated successfully, but these errors were encountered: