Is there an existing issue for this?
Current Behavior
In the current jellyfin.subdomain.conf.sample, the line add_header Access-Control-Allow-Origin "luna://com.webos.service.config" always; prevents the add_header lines in ssl.conf from applying.
For example, in ssl.conf, none of the uncommented headers are used:
# Optional additional headers
#add_header Cache-Control "no-transform" always;
add_header Content-Security-Policy "upgrade-insecure-requests; frame-ancestors 'self'" always;
#add_header Permissions-Policy "interest-cohort=()" always;
add_header Referrer-Policy "same-origin" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
#add_header X-UA-Compatible "IE=Edge" always;
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Robots-Tag "noindex, nofollow, nosnippet, noarchive";
Expected Behavior
The uncommented headers in ssl.conf should apply.
Steps To Reproduce
- Use the default provided jellyfin.subdomain.conf.sample config.
- Access Jellyfin
- Using the browser's web developer tools, notice none of the uncommented headers in ssl.conf are present
- Remove
add_header Access-Control-Allow-Origin "luna://com.webos.service.config" always; from jellyfin.subdomain.conf
- Check the headers in the browser again and notice they now appear
Is there an existing issue for this?
Current Behavior
In the current jellyfin.subdomain.conf.sample, the line
add_header Access-Control-Allow-Origin "luna://com.webos.service.config" always;prevents the add_header lines in ssl.conf from applying.For example, in ssl.conf, none of the uncommented headers are used:
Expected Behavior
The uncommented headers in ssl.conf should apply.
Steps To Reproduce
add_header Access-Control-Allow-Origin "luna://com.webos.service.config" always;from jellyfin.subdomain.conf