Serve static files from second domain as an alternative to setting CSP

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • jenkins-2.200

      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.

            Assignee:
            Daniel Beck
            Reporter:
            Daniel Beck
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: