Access-Control-Allow-Origin different for userContent rather than build pages?

21 views
Skip to first unread message

Jonathan Hodgson

unread,
Aug 14, 2016, 12:17:17 PM8/14/16
to Jenkins Users
Hi,

I have anartifacts, which are xml logs from MSBuild.

Now in my build description I have a HTML and some javascript which reads those files and shows me which architectures and configurations have warnings or errors.

That bit works fine, as each build completes, its associated cell in the table goes green, yellow or red, and I see the number of errors and warnings.

So far so good.

But as well as colouring the cell, and showing the number of errors/warnings, the code also and an href to an HTML file in userConten   with a GET parameter in the URL giving the location of one of the xml log which uses javascript and xslt to create a moe complete build log.

I prefer to keep that file separate from the the build so that I can improve the rendering of the log over time.

Anyway, that doesn't work.

Note that I've tested the html and javascript in python simpleHTTP server, and they work correctly.

But when I'm accessing it from Jenkins I get

SEC7120: Origin http:/<jenkins_ip_address>:8080 not found in Access-Control-Allow-Origin header.

in the console browser (Microsoft Edge, Chrome gives basically the same error, but is more verbose).

This despute the fact that I'm trying to read he same xml file, in the same way, as succeeded in the javascript in the build page description.

Does anybody have any idea what's going on? And hopefully a solution/workaround.

regards

Jon
Reply all
Reply to author
Forward
0 new messages