-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
[BUG] mjs files get an Content-Type of octet-stream while beeing a javascript file #388
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Same issue. I'll add the link to the Nextcloud/logging issue and specific comment for added context: |
It's an upstream issue. Out of our control. |
It's not an upstream issue. We need to add it to our nginx config, as seen here: https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html
|
I added this in my Nginx Proxy Manager for my Nextcloud-Domain, though logging is still empty. |
After the updated "site-confs/default.conf", I get this: IIRC, this happens due to
Since that file isn't owned by the PUID that launches the container, it will be recreated as is, even if edited. Any thoughts on how to clear it? |
Yeah we missed it in our testing, we've just kicked off a new build that should fix it if you update your conf again. |
Sorry to say but it broke more than it fixed. Had to revert image to ls291, nginx.conf && site-confs/default.conf to those versions. Sorry for no screenshots but if needed, I can redo it again now that I know how to go back. |
Is there an existing issue for this?
Current Behavior
request of logging.mjs fails as content type is octet-stream (which browser refuses to handle as javascript file)
Expected Behavior
mjs file has the correct content type of text/javascript
Steps To Reproduce
Setup nextcloud with the current image (nextcloud version 28) and access the logging tab.
This is AFAIK the first occurrence of such files yet
Environment
No response
CPU architecture
x86-64
Docker creation
docker compose up (as documented in README)
Container logs
Hint:
Official documentation got changed so it includes now the following snippet(commit):
The text was updated successfully, but these errors were encountered: