On Mon, Oct 20, 2014 at 8:30 AM, teilo <[email protected]> wrote: > Any other suggestions?
The traditional “fix” is to serve such content from a different domain. Obviously that is impractical to arrange for Jenkins generally. You could use <iframe sandbox> if you just want to render content visually and do not care about mechanical access. You may be able to use Content-Security-Policy for this purpose. If it works, that would be cleanest. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
