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
Incorrect mime-type for configuration.js #241
Comments
Thanks for spotting this! Yes, the content type should be relatively easy to set... I will have a look. Can you share the cloudron configuration? I am interested :) #143 |
I created this to correctly set the mime type in flask automatically. However some are not set on OWC side - not flasks fault. |
Great, thanks for the fast fix. I've just built an app package from that sha and it works as expected! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, first of all thanks for the great app! I am currently packaging it for Cloudron and came across an issue, where our reverse proxy in front of the app sets
X-Content-Type-Options: nosniff
which results in the browser refusing to use for example .js files which have the wrongcontent-type
header. The first such issue I came across was the configuration.js route which is delivered astext/html
.For example firefox will report as:
I am not a python developer or know flask much, but is there a way to set the content type correctly or am I totally on the wrong path here?
Potentially other routes also have the wrong mime-type, will get to that later if any.
We're using Polar.sh so you can upvote and help fund this issue. We receive the funding once the issue is completed & confirmed by you. Thank you in advance for helping prioritize & fund our work.
The text was updated successfully, but these errors were encountered: