Use HTTPS URLs for projects and other links where available #142
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.
In accordance with this project itself adopting modern web best practices, a number of plain HTTP URLs were found in both the "Why" section and in the project list (i.e. the links to the projects' homepages). All of the former, and most of the latter either offered HTTPS by default or optionally per my testing. Therefore, these URLs were updated accordingly, and confirmed to function.
It also might be a good idea to include, as a comment in the Projects list file, something like
To conform to modern best practices, all project URLs should use HTTPS if available
. However, as formally making such a recommendation is well beyond my pay grade, I didn't actually make any such change for the time being.