Fix HTTPS mixed content issue #1888
Merged
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 24 commits
January 27, 2016 22:26
This was referenced Jan 27, 2016
Open
Member
|
Thank you very much. Does that cause a problem for HTTP? |
Contributor
Author
|
@hikalkan No, it does not cause any problem with HTTP. It's better to enforce HTTPS for the fonts, even if you still use HTTP for the main website. Soon, HTTP will be marked as non-secure. It's better to begin the switch. IMHO #1888 is a better fix than #1765. |
Contributor
Author
|
@hikalkan Hi. Any news? |
hikalkan
added a commit
that referenced
this pull request
Feb 12, 2016
Fix HTTPS mixed content issue
Member
|
Thank you very much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi,
@hikalkan
As you can see, it fixes HTTPS mixed content issue.
Thanks to merge.
Sincerely,
HLFH