12 files changed, 21 insertions, 21 deletions
diff --git a/doc/dieshdiedie.html b/doc/dieshdiedie.html
index 9dd2313..75e660f 100644
--- a/doc/dieshdiedie.html
+++ b/doc/dieshdiedie.html
@@ -26,7 +26,7 @@
  One of the most frequent sources of security problems in programs
 is <em>parsing</em>. Parsing is a complex operation, and it is easy to
 make mistakes while designing and implementing a parser. (See
-<a href="http://cr.yp.to/qmail/guarantee.html">what Dan Bernstein says
+<a href="https://cr.yp.to/qmail/guarantee.html">what Dan Bernstein says
 on the subject</a>, section 5.)
 </p>
 
@@ -34,12 +34,12 @@ on the subject</a>, section 5.)
  But shells parse all the time. Worse, the <em>essence</em>
 of the shell is parsing: the parser and the runner are intimately
 interleaved and cannot be clearly separated, thanks to the
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">specification</a>.
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">specification</a>.
 The shell performs several kinds of expansions, automatic filename
 globbing, and automatic word splitting, in an unintuitive order,
 requiring users to memorize numerous arbitrary quoting rules in
 order to achieve what they want. Pages
-<a href="http://www.google.com/search?q=shell+script+pitfalls">abound</a>
+<a href="https://www.google.com/search?q=shell+script+pitfalls">abound</a>
 where common mistakes are listed, more often than not leading to
 security holes. Did you know that <tt>"$@"</tt> is a special case
 of double quoting, because it will split the arguments into
@@ -80,7 +80,7 @@ cannot be used safely with the normalized options, because most shells
 come with a builtin <tt>test</tt> that does <em>not</em> respect the
 specification to the letter. And let's not get started about <tt>echo</tt>,
 which has its own set of problems. Rich Felker has
-<a href="http://www.etalabs.net/sh_tricks.html">a page</a> listing tricks
+<a href="http://etalabs.net/sh_tricks.html">a page</a> listing tricks
 to use to write portable shell scripts. Writing a portable script should
 not be that hard.
 </p>
@@ -128,7 +128,7 @@ you will find with execline, and it is common to every script language.
 <p>
  The real solution to this portability problem is a convention that
 guarantees fixed absolute paths for executables, which the FHS does not do.
-The <a href="http://cr.yp.to/slashpackage.html">slashpackage</a> convention is
+The <a href="https://cr.yp.to/slashpackage.html">slashpackage</a> convention is
 such an initiative, and is well-designed; but as with every
 convention, it only works if everyone follows it, and unfortunately,
 slashpackage has not
@@ -143,7 +143,7 @@ can be configured to follow the slashpackage convention.
  I originally wanted a shell that could be used on an embedded system.
 Even the <tt>ash</tt> shell seemed big, so I thought of writing my
 own. Hence I had a look at the
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">sh
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">sh
 specification</a>... and ran away screaming.
 This specification
 is <em>insane</em>. It goes against every good programming
@@ -155,7 +155,7 @@ to wannabe <tt>sh</tt> implementors.
  POSIX cannot really be blamed for that: it only normalizes existing, historical
 behaviour. One can argue whether it is a good idea to normalize atrocious
 behaviour for historical reasons, as is the case with the infamous
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/gets.html">gets</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/gets.html">gets</a>
 function, but this is the way it is.
 </p>
 
diff --git a/doc/el_substitute.html b/doc/el_substitute.html
index 84b1985..3bb56a2 100644
--- a/doc/el_substitute.html
+++ b/doc/el_substitute.html
@@ -292,7 +292,7 @@ you can try to do better than these people:
  <li><a href="http://jriou.org/">Jo&euml;l Riou</a>
 wrote the <a href="quine-jriou.txt">first execlineb quine</a>, using
 only <tt>echo</tt> as non-execline external command. </li>
- <li> Shortly after, <a href="http://code.dogmap.org/">Paul Jarc</a>
+ <li> Shortly after, <a href="https://code.dogmap.org/">Paul Jarc</a>
 wrote a <a href="quine-prj.txt">much shorter quine</a>, using
 <tt>echo</tt> and <tt>env</tt> as non-execline external commands. He
 also wrote a <a href="quine-prj-2.txt">revised version</a>, using only
diff --git a/doc/el_transform.html b/doc/el_transform.html
index f33c576..cb163a8 100644
--- a/doc/el_transform.html
+++ b/doc/el_transform.html
@@ -163,7 +163,7 @@ as <em>n</em> separate words. </li>
 </a>
 
 <p>
- <a href="http://cr.yp.to/proto/netstrings.txt">Netstrings</a> are
+ <a href="https://cr.yp.to/proto/netstrings.txt">Netstrings</a> are
 a way to reliably encode strings containing arbitrary characters.
 <tt>execline</tt> takes advantage of this to offer a completely safe
 splitting mechanism. If a substitution command is given an empty
diff --git a/doc/elglob.html b/doc/elglob.html
index 3df2541..0870d2d 100644
--- a/doc/elglob.html
+++ b/doc/elglob.html
@@ -31,7 +31,7 @@ another program.
 
 <ul>
  <li> <tt>elglob</tt> performs
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/glob.html">globbing</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/glob.html">globbing</a>
 on <em>pattern</em>. </li>
  <li> It then performs
 <a href="el_substitute.html">variable substitution</a> on
diff --git a/doc/execline-cd.html b/doc/execline-cd.html
index 911eb2a..18759d1 100644
--- a/doc/execline-cd.html
+++ b/doc/execline-cd.html
@@ -31,7 +31,7 @@ given directory, then executes a program.
 
 <p>
 <tt>execline-cd</tt> performs a
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/chdir.html">chdir()</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/chdir.html">chdir()</a>
 system call on <em>dir</em>, then execs into <em>prog...</em>.
 </p>
 
diff --git a/doc/exitcodes.html b/doc/exitcodes.html
index 51902f1..619f5d3 100644
--- a/doc/exitcodes.html
+++ b/doc/exitcodes.html
@@ -30,7 +30,7 @@ to <em>C</em>, with as much precision as possible&nbsp;?
 <p>
  The problem is, there's more information in a wstat (the
 structure filled in by
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/waitpid.html">waitpid()</a>)
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/waitpid.html">waitpid()</a>)
 than a process can report by
 simply exiting. <em>P</em> could exit with the same exit code as <em>C</em>,
 but then what should it do if C has been killed by a signal&nbsp;?
@@ -52,7 +52,7 @@ can report.
 
 <p>
 Shells have their own
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_02">convention</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_02">convention</a>
 for reporting crashes, but since any exit code greater than 127 is reported
 as is, the information given by the shell is unreliable: "child exited 129"
 and "child was killed by SIGHUP" are indistinguishable. When shells get
diff --git a/doc/fdreserve.html b/doc/fdreserve.html
index cc808da..2412b5e 100644
--- a/doc/fdreserve.html
+++ b/doc/fdreserve.html
@@ -85,7 +85,7 @@ may fail, because <em>oldfd</em> and <em>newfd</em> may be the same.
 To avoid that, you should make sure that all descriptors returned by
 <tt>fdreserve</tt> are actually allocated before calling <tt>fdreserve</tt>
 again.
-(Thanks to <a href="http://code.dogmap.org/">Paul Jarc</a> for having
+(Thanks to <a href="https://code.dogmap.org/">Paul Jarc</a> for having
 spotted that case.)
 </p>
 
diff --git a/doc/getcwd.html b/doc/getcwd.html
index 2f040db..9735630 100644
--- a/doc/getcwd.html
+++ b/doc/getcwd.html
@@ -43,7 +43,7 @@ execs into <em>prog</em> with its arguments.
  <li> <em>var</em> must be given without a dollar&nbsp;! </li>
  <li> <em>var</em> must not contain <tt>=</tt>. </li>
  <li> Unlike the
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/utilities/pwd.html">pwd</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pwd.html">pwd</a>
 POSIX command, <tt>getcwd</tt> does not depend on the PWD environment
 variable and will exhibit a consistent behaviour no matter the environment. </li>
 </ul>
diff --git a/doc/grammar.html b/doc/grammar.html
index de8f4cf..419c13e 100644
--- a/doc/grammar.html
+++ b/doc/grammar.html
@@ -38,8 +38,8 @@ instance, the <tt>nice</tt> command works that way:
 <pre> nice -10 echo blah </pre> will read <tt>nice</tt> and <tt>-10</tt>
 from the argv, change the process' <em>nice</em> value, then exec into
 the command <tt>echo blah</tt>. This is called
-<a href="http://en.wikipedia.org/wiki/Chain_loading">chain loading</a>
-by some people, and <a href="http://www.faqs.org/docs/artu/ch07s02.html">
+<a href="https://en.wikipedia.org/wiki/Chain_loading">chain loading</a>
+by some people, and <a href="https://www.faqs.org/docs/artu/ch07s02.html">
 Bernstein chaining</a> by others. </li>
  <li> The purpose of the environment is to preserve some state across
 <tt>execve()</tt> calls. This state is usually small: most programs
diff --git a/doc/index.html b/doc/index.html
index aa11b20..cb411a6 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -60,7 +60,7 @@ library. </li>
 
 <p>
  execline is free software. It is available under the
-<a href="http://opensource.org/licenses/ISC">ISC license</a>.
+<a href="https://opensource.org/licenses/ISC">ISC license</a>.
 </p>
 
 <h3> Download </h3>
@@ -213,7 +213,7 @@ to your installation: the shebang lines for your system might be something like
 <a href="http://jriou.org/">Jo&euml;l Riou</a>. The only
 external command used is <tt>echo</tt>. </li>
 <li> Another <a href="quine-prj.txt">quine</a>, provided by
-<a href="http://code.dogmap.org/">Paul Jarc</a>. It is much shorter, but
+<a href="https://code.dogmap.org/">Paul Jarc</a>. It is much shorter, but
 uses the external commands <tt>echo</tt> and <tt>env</tt>. Later, Paul rewrote
 it <a href="quine-prj-2.txt">using only <tt>echo</tt></a>, then
 <a href="quine-prj-3.txt">using only <tt>echo</tt> and the environment</a>. </li>
diff --git a/doc/multisubstitute.html b/doc/multisubstitute.html
index 99994df..aebdde8 100644
--- a/doc/multisubstitute.html
+++ b/doc/multisubstitute.html
@@ -110,7 +110,7 @@ substitutions, whereas parallel substitution pays the price only once.
 <h2> Credits </h2>
 
 <p>
-<a href="http://code.dogmap.org/">Paul Jarc</a> first originated the
+<a href="https://code.dogmap.org/">Paul Jarc</a> first originated the
 idea of the <tt>multisubstitute</tt> command and a possible syntax.
 </p>
 
diff --git a/doc/runblock.html b/doc/runblock.html
index b5cc65b..7e77102 100644
--- a/doc/runblock.html
+++ b/doc/runblock.html
@@ -74,7 +74,7 @@ an execline script, using the <a href="ifte.html">ifte</a> command.
 
 <p>
  The <tt>runblock</tt> idea, as well as the <tt>ifelse</tt> idea, comes
-from <a href="http://code.dogmap.org/">Paul Jarc</a>.
+from <a href="https://code.dogmap.org/">Paul Jarc</a>.
 </p>
 
 </body>