Gatling reports stopped working after Jenkins update

[Johannes Eickhold]

Hi,

after we updated Jenkins to ver. 1.642.1 the Gatling reports (reachable via the Gatling plugin) stopped working.

I get this errors on my browser's console:

Blocked script execution in 'http://yyy:8888/me/my-views/view/All/job/Performance-Test/22/gatling/report/yyy/source/' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

(index):19 Uncaught SecurityError: Sandbox access violation: Blocked a frame at "http://yyy:8888" from accessing a frame at "http://yyy:8888".  The frame being accessed is sandboxed and lacks the "allow-same-origin" flag.

Any ideas how this can be fixed?

Is it a problem of the plug-in or a problem of the latest Jenkins version?

We are using version 1.1.1 of the Gatling plugin now and before the update.

Greets,

Johannes.

[Victor Martinez]

Hi,

Look at:

- https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy

Reason: 

- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09

Further details:

- https://issues.jenkins-ci.org/browse/JENKINS-32026

Cheers

[Johannes Eickhold]

Thanks Victor,

as a workaround I could get the reports showing properly again by opting out of the new CSP header as described in your second link.

On the Jenkins script console I issued a:

System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "")

Maybe this could also be fixed upstream in the Gatling plugin?

Cheers,

Johannes.