avoid mixed-content issues in the profiler output #189
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
loading the css/js over https in an http page has no negative side-effects but using http in an https page will cause some browsers to not load the assets due to mixed-content restrictions
rurban
pushed a commit
that referenced
this pull request
Oct 4, 2014
avoid mixed-content issues in the profiler output
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.
loading the css/js over https in an http page has no negative side-effects
but using http in an https page will cause some browsers to not load the
assets due to mixed-content restrictions
For example: https://viennan.net/profile-1412355279.48924.html (tested with Firefox 32)