Skip to content

Use HTTPS URLs instead of HTTP URLs where appropriate #20807

@practicalswift

Description

@practicalswift

Due to legacy reasons our documentation and code comments contain a lot of HTTP URLs to resources which are nowadays served also under the corresponding HTTPS URL.

It would be nice if we used HTTPS URLs where possible.

The following command can be used to find URL candidates for such cleanup (excluding the many http://www.opensource.org/licenses/mit-license.php links):

$ git grep 'http://' -- ":(exclude)*.vcxproj*"  ":(exclude)*.svg" ":(exclude)doc/release-notes/" \
      ":(exclude)src/leveldb/" ":(exclude)src/secp256k1/" ":(exclude)src/univalue/" ":(exclude)src/crc32c/" \
      ":(exclude)src/crypto/ctaes/" ":(exclude)src/tinyformat.h" | \
      grep -v 'http://www.opensource.org/licenses/mit-license.php'

Each of the URLs returned by the above command would have to be manually checked for HTTPS availability before changing the URL.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions