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 vote

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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

13,558 views 16 15
Join discussion

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