docs: Update old external links to use HTTPS where possible

docs/brand-guide.rst

@@ -43,7 +43,7 @@ Solidity Logo License
   :alt: Creative Commons License
 
 The Solidity logo is distributed and licensed under a `Creative Commons
-Attribution 4.0 International License <http://creativecommons.org/licenses/by/4.0/>`_.
+Attribution 4.0 International License <https://creativecommons.org/licenses/by/4.0/>`_.
 
 This is the most permissive Creative Commons license and allows reuse
 and modifications for any purpose.

docs/contributing.rst

@@ -254,7 +254,7 @@ inside the input. We have a specialized binary called ``solfuzzer`` which takes
 and fails whenever it encounters an internal compiler error, segmentation fault or similar, but
 does not fail if e.g., the code contains an error. This way, fuzzing tools can find internal problems in the compiler.
 
-We mainly use `AFL <http://lcamtuf.coredump.cx/afl/>`_ for fuzzing. You need to download and
+We mainly use `AFL <https://lcamtuf.coredump.cx/afl/>`_ for fuzzing. You need to download and
 install the AFL packages from your repositories (afl, afl-clang) or build them manually.
 Next, build Solidity (or just the ``solfuzzer`` binary) with AFL as your compiler:
 
@@ -388,7 +388,7 @@ local slang and references, making your language as clear to all readers as poss
 Title Case for Headings
 -----------------------
 
-Use `title case <http://titlecase.com>`_ for headings. This means capitalise all principal words in
+Use `title case <https://titlecase.com>`_ for headings. This means capitalise all principal words in
 titles, but not articles, conjunctions, and prepositions unless they start the
 title.
 

docs/index.rst

@@ -72,10 +72,10 @@ Community volunteers help translate this documentation into several languages.
 They have varying degrees of completeness and up-to-dateness. The English
 version stands as a reference.
 
-* `French <http://solidity-fr.readthedocs.io>`_ (in progress)
+* `French <https://solidity-fr.readthedocs.io>`_ (in progress)
 * `Italian <https://github.com/damianoazzolini/solidity>`_ (in progress)
 * `Japanese <https://solidity-jp.readthedocs.io>`_
-* `Korean <http://solidity-kr.readthedocs.io>`_ (in progress)
+* `Korean <https://solidity-kr.readthedocs.io>`_ (in progress)
 * `Russian <https://github.com/ethereum/wiki/wiki/%5BRussian%5D-%D0%A0%D1%83%D0%BA%D0%BE%D0%B2%D0%BE%D0%B4%D1%81%D1%82%D0%B2%D0%BE-%D0%BF%D0%BE-Solidity>`_ (rather outdated)
 * `Simplified Chinese <https://learnblockchain.cn/docs/solidity/>`_ (in progress)
 * `Spanish <https://solidity-es.readthedocs.io>`_

docs/installing-solidity.rst

@@ -205,7 +205,7 @@ The following are dependencies for all builds of Solidity:
 | `cvc4`_ (Optional)                | For use with SMT checker.                             |
 +-----------------------------------+-------------------------------------------------------+
 
-.. _cvc4: http://cvc4.cs.stanford.edu/web/
+.. _cvc4: https://cvc4.cs.stanford.edu/web/
 .. _Git: https://git-scm.com/download
 .. _Boost: https://www.boost.org
 .. _CMake: https://cmake.org/download/
@@ -243,7 +243,7 @@ command-line builds:
 
     sudo xcodebuild -license accept
 
-Our OS X build script uses `the Homebrew <http://brew.sh>`_
+Our OS X build script uses `the Homebrew <https://brew.sh>`_
 package manager for installing external dependencies.
 Here's how to `uninstall Homebrew
 <https://docs.brew.sh/FAQ#how-do-i-uninstall-homebrew>`_,

docs/introduction-to-smart-contracts.rst

@@ -285,7 +285,7 @@ likely it will be.
     since it is not up to the submitter of a transaction, but up to the miners to determine in which block the transaction is included.
 
     If you want to schedule future calls of your contract, you can use
-    the `alarm clock <http://www.ethereum-alarm-clock.com/>`_ or a similar oracle service.
+    the `alarm clock <https://www.ethereum-alarm-clock.com/>`_ or a similar oracle service.
 
 .. _the-ethereum-virtual-machine:
 

docs/resources.rst

@@ -80,7 +80,7 @@ Solidity Integrations
 
 * Visual Studio Code:
 
-    * `Visual Studio Code extension <http://juan.blanco.ws/solidity-contracts-in-visual-studio-code/>`_
+    * `Visual Studio Code extension <https://juan.blanco.ws/solidity-contracts-in-visual-studio-code/>`_
         Solidity plugin for Microsoft Visual Studio Code that includes syntax highlighting and the Solidity compiler.
 
 Discontinued:

docs/style-guide.rst

@@ -1145,7 +1145,7 @@ NatSpec
 Solidity contracts can have a form of comments that are the basis of the
 Ethereum Natural Language Specification Format.
 
-Add comments above functions or contracts following `doxygen <http://www.doxygen.nl>`_ notation
+Add comments above functions or contracts following `doxygen <https://www.doxygen.nl>`_ notation
 of one or multiple lines starting with ``///`` or a
 multiline comment starting with ``/**`` and ending with ``*/``.
 

docs/units-and-global-variables.rst

@@ -201,7 +201,7 @@ Mathematical and Cryptographic Functions
 
     If you use ``ecrecover``, be aware that a valid signature can be turned into a different valid signature without
     requiring knowledge of the corresponding private key. In the Homestead hard fork, this issue was fixed
-    for _transaction_ signatures (see `EIP-2 <http://eips.ethereum.org/EIPS/eip-2#specification>`_), but
+    for _transaction_ signatures (see `EIP-2 <https://eips.ethereum.org/EIPS/eip-2#specification>`_), but
     the ecrecover function remained unchanged.
 
     This is usually not a problem unless you require signatures to be unique or

scripts/install_deps.sh

@@ -101,7 +101,7 @@ case $(uname -s) in
         esac
 
         # Check for Homebrew install and abort if it is not installed.
-        brew -v > /dev/null 2>&1 || { echo >&2 "ERROR - solidity requires a Homebrew install.  See http://brew.sh."; exit 1; }
+        brew -v > /dev/null 2>&1 || { echo >&2 "ERROR - solidity requires a Homebrew install.  See https://brew.sh."; exit 1; }
         brew update
         brew install boost
         brew install cmake