Fixed #25778 -- Updated docs links to use https when available.

docs/topics/http/_images/middleware.graffle

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 	<key>ActiveLayerIndex</key>

docs/topics/http/sessions.txt

@@ -165,7 +165,7 @@ and the :setting:`SECRET_KEY` setting.
 
     Finally, the size of a cookie can have an impact on the `speed of your site`_.
 
-.. _`common limit of 4096 bytes`: http://tools.ietf.org/html/rfc2965#section-5.3
+.. _`common limit of 4096 bytes`: https://tools.ietf.org/html/rfc2965#section-5.3
 .. _`replay attacks`: https://en.wikipedia.org/wiki/Replay_attack
 .. _`speed of your site`: http://yuiblog.com/blog/2007/03/01/performance-research-part-3/
 

docs/topics/http/shortcuts.txt

@@ -199,7 +199,7 @@ You can use the :func:`redirect` function in a number of ways.
 
         def my_view(request):
             ...
-            return redirect('http://example.com/')
+            return redirect('https://example.com/')
 
 By default, :func:`redirect` returns a temporary redirect. All of the above
 forms accept a ``permanent`` argument; if set to ``True`` a permanent redirect

docs/topics/http/urls.txt

@@ -179,10 +179,10 @@ What the URLconf searches against
 The URLconf searches against the requested URL, as a normal Python string. This
 does not include GET or POST parameters, or the domain name.
 
-For example, in a request to ``http://www.example.com/myapp/``, the URLconf
+For example, in a request to ``https://www.example.com/myapp/``, the URLconf
 will look for ``myapp/``.
 
-In a request to ``http://www.example.com/myapp/?page=3``, the URLconf will look
+In a request to ``https://www.example.com/myapp/?page=3``, the URLconf will look
 for ``myapp/``.
 
 The URLconf doesn't look at the request method. In other words, all request