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

X-Content-Type-Options nosniif blocking javascript missing MIME type #32456

Closed
crutchfield opened this issue May 18, 2024 · 5 comments
Closed

Comments

@crutchfield
Copy link

Description:

MIME type appears to be missing on javascript, meteor_runtime_config.js.

Steps to reproduce:

  1. Fresh install of 6.8.0 via docker
  2. Register
  3. Logout and attempt to log back in

Expected behavior:

Expected login screen or application to appear

Actual behavior:

Got "loading" dots
image

Server Setup Information:

  • Version of Rocket.Chat Server: 6.8.0
  • Operating System: Amazon Linux 2023
  • Deployment Method: Docker (Nginx reverse proxy)
  • Number of Running Instances: 1
  • DB Replicaset Oplog: yes
  • NodeJS Version: (From docker image)
  • MongoDB Version: 5.0

Client Setup Information

  • Desktop App or Browser Version: Firefox 115.10.0esr (64-bit), Chrome 124.0.6367.208 (Official Build) (64-bit)
  • Operating System: Amazon Linux 2023 and Microsoft Windows 2022 Datacenter

Additional context

Get same behavoir from both linux/firefox and windows/chrome.

Relevant logs:

Firefox console

The resource from “https://rocketchat2.pcms.internal/meteor_runtime_config.js?hash=b9db519591a16fd9eb3f010d6086859eb693e884” was blocked due to MIME type (“”) mismatch (X-Content-Type-Options: nosniff). rocketchat2.pcms.internal

Chrome console
image

@crutchfield
Copy link
Author

Falling back to release 6.7.2 does not have same issue.

@szmarczak
Copy link

szmarczak commented May 18, 2024

Looks like a duplicate of #30717 #30938

Also I'm encountering the same issue. Looks like RocketChat is a no-go for me :(

@crutchfield
Copy link
Author

Agree it does appear to be a duplicate.

@DialogIntelligens
Copy link

Did you fix it?

@crutchfield
Copy link
Author

The issues they referenced appear to still be open. That is why I felt closing as a duplicate was appropriate. Expecting them to address the issue through the earlier reported issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants