do not set X-Content-Security-Policy header #135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All major browsers support Content-Security-Policy header since a long time. Only Internet Explorer 11 does not support it. But it also only supports `sandbox` directive by X-Content-Security-Policy header. The sandbox is not useful at all for Ember applications cause it could only be used to disable all scripts. As an Ember applicaiton is not usable at all without JavaScript that is not a reasonable configuration.
|
@jelhan Great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All major browsers support Content-Security-Policy header since a long time. Only Internet Explorer 11 does not support it. But it also only supports
sandboxdirective by X-Content-Security-Policy header. The sandbox is not useful at all for Ember applications cause it could only be used to disable all scripts. As an Ember applicaiton is not usable at all without JavaScript that is not a reasonable configuration.This resolves the inconsistency between middleware used in Ember CLI's development server and FastBoot initalizier described in #133.