Use TLS/SSL for all SRFI URLs.

Author: arthurgleckler

srfi-64.html

@@ -29,21 +29,21 @@ <H1>Status</H1>
 
 This SRFI is currently in ``final'' status. To see an explanation of each
 status that a SRFI can hold, see
-<a href="http://srfi.schemers.org/srfi-process.html">here</a>.
+<a href="https://srfi.schemers.org/srfi-process.html">here</a>.
 It will remain in draft status until 2005-03-17, or as amended. To
 provide input on this SRFI, please <code>
 <a href="mailto:srfi minus 64 at srfi dot schemers dot org">mailto:srfi minus 64 at srfi dot schemers dot org</a></code>.
-See <a href="http://srfi.schemers.org/srfi-list-subscribe.html">instructions
+See <a href="https://srfi.schemers.org/srfi-list-subscribe.html">instructions
 here</a> to subscribe to the list. You can access previous messages via
-<a href="http://srfi.schemers.org/srfi-64/mail-archive/maillist.html">the
+<a href="https://srfi.schemers.org/srfi-64/mail-archive/maillist.html">the
 archive of the mailing list</a>.
 <p>
 <ul>
   <li>Received: 2005-01-07</li>
   <li>Draft: 2005-01-28--2005-03-28</li>
-  <li>Revised: <a href="http://srfi.schemers.org/srfi-64/srfi-64-1.3.html">2005-10-18</a>  
-  <li>Revised: <a href="http://srfi.schemers.org/srfi-64/srfi-64-1.5.html">2006-02-24</a>  
-  <li>Final: <a href="http://srfi.schemers.org/srfi-64/srfi-64-1.6.html">2006-06-18</a></li>
+  <li>Revised: <a href="https://srfi.schemers.org/srfi-64/srfi-64-1.3.html">2005-10-18</a>  
+  <li>Revised: <a href="https://srfi.schemers.org/srfi-64/srfi-64-1.5.html">2006-02-24</a>  
+  <li>Final: <a href="https://srfi.schemers.org/srfi-64/srfi-64-1.6.html">2006-06-18</a></li>
   <li>Revised to fix errata: 2016-08-11</li>
 </ul>
 </p>
@@ -220,9 +220,9 @@ <h3>Tests for catching errors</h3>
 specification) what form <code><var>test-error</var></code> may take,
 though all implementations must allow <code>#t</code>.
 Some implementations may support
-<a href="http://srfi.schemers.org/srfi-35/srfi-35.html">SRFI-35's conditions</a>,
+<a href="https://srfi.schemers.org/srfi-35/srfi-35.html">SRFI-35's conditions</a>,
 but these are only standardized for 
-<a href="http://srfi.schemers.org/srfi-36/srfi-36.html">SRFI-36's I/O conditions</a>, which are seldom useful in test suites.
+<a href="https://srfi.schemers.org/srfi-36/srfi-36.html">SRFI-36's I/O conditions</a>, which are seldom useful in test suites.
 An implementation may also allow implementation-specific
 <q>exception types</q>.
 For example Java-based implementations may allow
@@ -505,7 +505,7 @@ <h2>Test-runner</h2>
 <code>(<b>test-runner-current</b> <var>runner</var>)</code><br />
 Get or set the current test-runner.
 If an implementation supports parameter objects
-(as in <a href="http://srfi.schemers.org/srfi-39/srfi-39.html">SRFI-39</a>),
+(as in <a href="https://srfi.schemers.org/srfi-39/srfi-39.html">SRFI-39</a>),
 then <code>test-runner-current</code> can be a parameter object.
 Alternatively, <code>test-runner-current</code> may be implemented
 as a macro or function 
@@ -822,7 +822,7 @@ <h3>Example</h3>
 <h1>Implementation</h1>
 <p>
 The test implementation uses <code>cond-expand</code>
-(<a href="http://srfi.schemers.org/srfi-0/srfi-0.html">SRFI-0</a>)
+(<a href="https://srfi.schemers.org/srfi-0/srfi-0.html">SRFI-0</a>)
 to select different code depending on certain SRFI names (<code>srfi-9</code>,
 <code>srfi-34</code>, <code>srfi-35</code>, <code>srfi-39</code>),
 or implementations (<code>kawa</code>).
@@ -833,8 +833,8 @@ <h1>Implementation</h1>
 <h2>Examples</h2>
 <p>Here is <a href="srfi-25-test.scm"><code>srfi-25-test.scm</code></a>,
 based converted from Jussi Piitulainen's
-<a href="http://srfi.schemers.org/srfi-25/test.scm"><code>test.scm</code></a>
-for <a href="http://srfi.schemers.org/srfi-25/srfi-25.html">SRFI-25</a>.</p>
+<a href="https://srfi.schemers.org/srfi-25/test.scm"><code>test.scm</code></a>
+for <a href="https://srfi.schemers.org/srfi-25/srfi-25.html">SRFI-25</a>.</p>
 
 <h2>Test suite</h2>
 <p>