HTTPS-ify lots of URLs, update some to their newer homes - #1157
Merged
Merged
Conversation
This matters for user security. I didn't touch blog posts & pages related to past conferences. The `content/docs` could be HTTPS-ified as well but it contains lots of HTTP links so maybe that'd be best done in a separate PR.
|
Deploy preview for reactjs ready! Built with commit 35e52fa |
Contributor
Author
|
Ping? There's been no reply for a month. |
Collaborator
|
Thank you! This is important 👍 |
mgol
added a commit
to mgol/reactjs.org
that referenced
this pull request
Feb 7, 2019
This is a followup to reactjs#1157
Contributor
Author
|
I've submitted a followup PR HTTPS-ifying |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This matters for user security.
I didn't touch blog posts & pages related to past conferences.
The
content/docscould be HTTPS-ified as well but it contains lots of HTTPlinks so maybe that'd be best done in a separate PR.