Remove distinction in http/https for requirejs-config.js #7010
Conversation
This file contains hidden or 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
added 3 commits
October 14, 2016 11:27
This code is only used for the generation of requirejs-config.js so removing the http/https distinction has no effect on other files. The contents of requirejs-config.js are exactly equal when requested over http as https.
…kContext::__construct
…ackContext::__construct
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.
This code is only used for the generation of requirejs-config.js so removing the http/https distinction has no effect on other files.
The contents of requirejs-config.js are exactly equal when requested over http as https and only the http variant is generated by running
magento setup:static-content:deployAfter this fix the generated file is also available for https requests.
Fixes #5977