Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.0.0-beta.2 web interface fails to load due to strict MIME rules #2052

Closed
aberenyi opened this issue Apr 12, 2016 · 2 comments
Closed

2.0.0-beta.2 web interface fails to load due to strict MIME rules #2052

aberenyi opened this issue Apr 12, 2016 · 2 comments
Assignees
Labels
web
Milestone

Comments

@aberenyi
Copy link

@aberenyi aberenyi commented Apr 12, 2016

Problem description

Web interface fails to load with error Refused to execute script from 'https://graylog.example.com/config.js' because its MIME type ('application/octet-stream') is not executable, and strict MIME type checking is enabled. when X-Content-Type-Options: nosniff header is present on the request.

Steps to reproduce the problem

  1. Set up nginx to proxy to the Graylog web interface port
  2. Add add_header X-Content-Type-Options nosniff; to the config

Environment

  • Graylog Version: 2.0.0-beta.2
  • Elasticsearch Version: 2.3.1-1
  • MongoDB Version: 3.2.3-2
  • Operating System: ArchLinux
  • Browser version: Chrome
@dennisoelkers dennisoelkers self-assigned this Apr 12, 2016
@dennisoelkers
Copy link
Member

@dennisoelkers dennisoelkers commented Apr 12, 2016

Hey @aberenyi,

thanks for reporting this. This issue has already been fixed and the fix will be included in the next beta which will be released this week.

@aberenyi
Copy link
Author

@aberenyi aberenyi commented Apr 12, 2016

joschi pushed a commit that referenced this issue Apr 12, 2016
@joschi joschi added this to the 2.0.0 milestone Apr 12, 2016
@joschi joschi added the web label Apr 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants