Make these various links secure

Those which remain plain http either didn't work on HTTPS when I
tried them or are local connections.

CHANGELOG.rst

@@ -1,4 +1,4 @@
 Change Log
 ==========
 
-Please see the `documentation <http://whitenoise.evans.io/en/stable/changelog.html>`_.
+Please see the `documentation <https://whitenoise.evans.io/en/stable/changelog.html>`_.

README.rst

@@ -46,5 +46,5 @@ Asked Questions`_.
 
 To get started, see the documentation_.
 
-.. _Infrequently Asked Questions: http://whitenoise.evans.io/en/stable/#infrequently-asked-questions
-.. _documentation: http://whitenoise.evans.io/en/stable/
+.. _Infrequently Asked Questions: https://whitenoise.evans.io/en/stable/#infrequently-asked-questions
+.. _documentation: https://whitenoise.evans.io/en/stable/

docs/base.rst

@@ -237,7 +237,7 @@ sub-classing WhiteNoise and setting the attributes directly.
     The W3C `explicitly state`__ that this behaviour is safe for publicly
     accessible files.
 
-.. __: http://www.w3.org/TR/cors/#security
+.. __: https://www.w3.org/TR/cors/#security
 
 .. attribute:: add_headers_function
 

docs/changelog.rst

@@ -300,7 +300,7 @@ v3.2
  * Fixed a bug where incorrect Content-Type headers were being sent on 304 Not
    Modified responses (thanks `@oppianmatt <https://github.com/oppianmatt>`_).
  * Return Vary and Cache-Control headers on 304 responses, as specified by the
-   `RFC <http://tools.ietf.org/html/rfc7232#section-4.1>`_.
+   `RFC <https://tools.ietf.org/html/rfc7232#section-4.1>`_.
 
 v3.1
 ----
@@ -334,7 +334,7 @@ v3.0
       import path **will continue to work** for now, but users are encouraged
       to update their code to use the new path.
 
-.. _WhiteNoise 2.x: http://whitenoise.evans.io/en/legacy-2.x/
+.. _WhiteNoise 2.x: https://whitenoise.evans.io/en/legacy-2.x/
 
 
 Simpler, cleaner Django middleware integration

docs/django.rst

@@ -720,7 +720,7 @@ Deploying an application which is not at the root of the domain
 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
 Sometimes Django apps are deployed at a particular prefix (or "subdirectory")
-on a domain e.g. http://example.com/my-app/ rather than just http://example.com.
+on a domain e.g. https://example.com/my-app/ rather than just https://example.com.
 
 In this case you would normally use Django's `FORCE_SCRIPT_NAME
 <https://docs.djangoproject.com/en/1.11/ref/settings/#force-script-name>`_

docs/flask.rst

@@ -96,7 +96,7 @@ By default, WhiteNoise will serve up static files from the URL root --
 i.e., ``http://localhost:5000/style.css``.
 
 To change that, set a `prefix
-<http://whitenoise.evans.io/en/stable/base.html#whitenoise-api>`_ string:
+<https://whitenoise.evans.io/en/stable/base.html#whitenoise-api>`_ string:
 
 .. code-block:: python
 

setup.py

@@ -24,7 +24,7 @@ def read(*path):
     version=version,
     author="David Evans",
     author_email="d@evans.io",
-    url="http://whitenoise.evans.io",
+    url="https://whitenoise.evans.io",
     packages=find_packages(exclude=["tests*"]),
     license="MIT",
     description="Radically simplified static file serving for WSGI applications",

whitenoise/base.py

@@ -38,7 +38,7 @@ class WhiteNoise(object):
     max_age = 60
     # Set 'Access-Control-Allow-Orign: *' header on all files.
     # As these are all public static files this is safe (See
-    # http://www.w3.org/TR/cors/#security) and ensures that things (e.g
+    # https://www.w3.org/TR/cors/#security) and ensures that things (e.g
     # webfonts in Firefox) still work as expected when your static files are
     # served from a CDN, rather than your primary domain.
     allow_all_origins = True

whitenoise/django.py

@@ -2,6 +2,6 @@
     "\n\n"
     "Your WhiteNoise configuration is incompatible with WhiteNoise v4.0\n"
     "This can be fixed by following the upgrade instructions at:\n"
-    "http://whitenoise.evans.io/en/stable/changelog.html#v4-0\n"
+    "https://whitenoise.evans.io/en/stable/changelog.html#v4-0\n"
     "\n"
 )

whitenoise/responders.py

@@ -19,7 +19,7 @@
 )
 
 # Headers which should be returned with a 304 Not Modified response as
-# specified here: http://tools.ietf.org/html/rfc7232#section-4.1
+# specified here: https://tools.ietf.org/html/rfc7232#section-4.1
 NOT_MODIFIED_HEADERS = (
     "Cache-Control",
     "Content-Location",