-
Notifications
You must be signed in to change notification settings - Fork 85
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 cant be dissabled #74
Comments
That isn't one of the configurable options so that functionality would need to be added, or you could override it using @app.after_request
def add_header(response):
# Force remove X-Content-Type-Options added by flask-talisman
del response.headers['X-Content-Type-Options']
return response |
I've opened a pull request #75. In this I've added the option to disable the X-Content-Type-Options header from being set. However the Travis CI check is getting an import error and I don't know how to fix it, could you look at that? |
I'm not sure how actively this repo is being maintained at the moment unfortunately :-( I've a few of my open PRs waiting too. @theacodes are you still maintaining this? It's complaining about coverage - though error messages are weird. I know when I submitted changes to here in the past it does insist on 100% pytest coverage so add a quick test to talisman_test.py and that might fix the error. Also wonder if you should add a similar option for |
As you've already seen I also added the option for |
I'm currently using talisman to set CSP, but I need to have X-Content-Type-Options disabled/not set. In the current version it is always set to 'nosniff'.
The text was updated successfully, but these errors were encountered: