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

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

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 Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

461 views 1 15
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot