Skip to content

Filter 'x-content-type-options' from twitter's response headers#3

Open
rmehner wants to merge 1 commit into
leftlogic:masterfrom
rmehner:filter-x-content-type-options
Open

Filter 'x-content-type-options' from twitter's response headers#3
rmehner wants to merge 1 commit into
leftlogic:masterfrom
rmehner:filter-x-content-type-options

Conversation

@rmehner
Copy link
Copy Markdown

@rmehner rmehner commented Sep 9, 2014

Twitter responds with x-content-type-options set to nosniff (rightfully so), unfortunately this leads to strict MIME errors when used in browsers (like we do with the twitterwall), so that the script is not executed:

reject_js_2014

This just filters this out from the response headers.

@brendanmullan
Copy link
Copy Markdown

Robin I tested that fix and it works perfectly, many thanks for that :-)

@dmelamedcl
Copy link
Copy Markdown

I believe the proper fix is rather to set the Content-Type to application/javascript

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

Successfully merging this pull request may close these issues.

3 participants