Dealing with Content-Security-Policy is just too annoying, and there's too many plugins trying to just serve static files in Jenkins, often for no real reason.
We need second domain support for static resources (DirectoryBrowserSupport) such that accessing that is possible without authentication, just with a token, and that token is used for linked resources as well.
- relates to
-
JENKINS-59849 Spaces don't work in resource root paths
- Closed
-
JENKINS-59874 Support resource domain
- Open
- links to