Anyone used issue collector with X-Content-Type: nosniff

PaulEvans-Splash January 25, 2018

Using the JIRA cloud service, and including an issue collector into one of our Symfony 3 projects. We find that the 'Report problem' button is displayed but cannot be clicked. Javascript console:

[Error] Failed to load resource: the server responded with a status of 404 (HTTP/2.0 404) (trigger, line 0)
[Error] Did not load script at 'https://oursubdomain.atlassian.net/rest/collectors/1.0/configuration/trigger/?os_authType=none&callback=trigger_' because non script MIME types are not allowed when 'X-Content-Type: nosniff' is given.

Anyone else hit this? Any thoughts on solving without removing the nosniff http header?

Thanks

Paul

1 answer

0 votes
PaulEvans-Splash February 7, 2018

This boiled down to the wrong issue collector code embedded in the page. An old probably no-longer existing code was being used. Replacing the code with that generated freshly cleared the issue in the page of concern. - Thanks to Atlassian support in troubleshooting.

Suggest an answer

Log in or Sign up to answer