<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">While going through the source for these updates, I made a few notes.<div><br></div><div>There are two links to <a href="http://collab.net" target="_blank">collab.net</a> that don't work very well:</div><div>* ch04-branching-and-merging.xml#svn.branchmerge.advanced.finalword</div><div>  There is an article written by Paul Burba about merge-info (<a href="http://www.open.collab.net/community/subversion/articles/merge-info.html" target="_blank">http://www.open.collab.net/community/subversion/articles/merge-info.html</a>). <a href="http://www.open.collab.net" target="_blank">www.open.collab.net</a> seems to respond and it even redirects to https, however the server doesn't support TLS 1.2 and the two browsers I tried (Firefox and Edge under Win11) both frowned upon the site. I was able to reach the site using Links (under Ubuntu).</div><div>* ch06-server-configuration.xml#svn.serverconfig.pathbasedauthz.gotchas</div><div>  There is a link to a blog post by C. Michael Pilato (<a href="http://blogs.collab.net/subversion/2007/03/authz_and_anon_/" target="_blank">http://blogs.collab.net/subversion/2007/03/authz_and_anon_/</a>) where I can't figure out a way to get the original content from <a href="http://collab.net" target="_blank">collab.net</a>. It is possible to access it through <a href="http://archive.org" target="_blank">archive.org</a> (<font color="#1155cc"><u><a href="https://web.archive.org/web/20130721090205/http://blogs.collab.net:80/subversion/authz_and_anon_">https://web.archive.org/web/20130721090205/http://blogs.collab.net:80/subversion/authz_and_anon_</a></u></font>). There is a TODO: note "Merge content from the blog post into the book".</div><div>Is it possible to rehost those? I assume copyright comes into play in delicate ways.<br></div><div><br></div><div>Regarding examples:</div><div>I changed one (1) pointing to <a href="http://svn.apache.org">svn.apache.org</a>. Most other were using <a href="http://example.com">example.com</a> and I didn't change those.</div><div>There are a few using <a href="http://svn.red-bean.com">http://svn.red-bean.com</a> (ch03-advanced-topics.xml#svn.advanced.pegrevs, ref-svn.xml#svn.ref.svn.c.blame). I'm not sure if they are supposed to be working examples (they currently DON'T work, with different error messages E170011: Repository moved permanently, E175003: The server at '...' does not support the HTTP/DAV protocol, svn: E235000: In file '../subversion/libsvn_client/util.c' line 96: assertion failed (svn_uri__is_ancestor(pathrev->repos_root_url, url))).</div><div>If they are supposed to be working, then someone should probably give the server some love and care. Otherwise we should probably rewrite them to <a href="http://example.com">example.com</a>. Thoughts?<br></div><div><br></div><div>Kind regards,</div><div>Daniel</div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Den fre 19 aug. 2022 kl 08:29 skrev <<a href="mailto:danielsahlberg@users.sourceforge.net" target="_blank">danielsahlberg@users.sourceforge.net</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Revision: 6057<br>
          <a href="http://sourceforge.net/p/svnbook/source/6057" rel="noreferrer" target="_blank">http://sourceforge.net/p/svnbook/source/6057</a><br>
Author:   danielsahlberg<br>
Date:     2022-08-19 06:28:42 +0000 (Fri, 19 Aug 2022)<br>
Log Message:<br>
-----------<br>
Replace http:// links with https:// and update links when the old target no longer exists.<br>
<br>
* en/book/appa-quickstart.xml<br>
  (svn.intro.install): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
<br>
* en/book/appc-webdav.xml<br>
  (svn.webdav.clients.standalone.free): <a href="http://www.ics.uci.edu/~webdav" rel="noreferrer" target="_blank">www.ics.uci.edu/~webdav</a> redirect to <a href="http://www.davexplorer.org" rel="noreferrer" target="_blank">www.davexplorer.org</a><br>
  (svn.webdav.clients.file-explorer-extensions.linux-de): s/http/https/ for <a href="http://gnome.org" rel="noreferrer" target="_blank">gnome.org</a> and <a href="http://kde.org" rel="noreferrer" target="_blank">kde.org</a> (and <a href="http://kde.org" rel="noreferrer" target="_blank">kde.org</a> seems to redirect www.k.o to k.o)<br>
  (svn.webdav.clients.fs-impl.windows): s/http/https/ for <a href="http://southrivertech.com" rel="noreferrer" target="_blank">southrivertech.com</a> (and it seems to redirect www.s.c to s.c)<br>
  (svn.webdav.clients.fs-impl.linux): s/http/https/ for <a href="http://nongnu.org" rel="noreferrer" target="_blank">nongnu.org</a><br>
<br>
* en/book/ch00-preface.xml<br>
  (svn.intro.righttool): s/http/https/ for <a href="http://git-scm.com" rel="noreferrer" target="_blank">git-scm.com</a> and <a href="http://mercurial-scm.org" rel="noreferrer" target="_blank">mercurial-scm.org</a> (and <a href="http://mercurial-scm.org" rel="noreferrer" target="_blank">mercurial-scm.org</a> seems to redirect <a href="http://mercurial-scm.org" rel="noreferrer" target="_blank">mercurial-scm.org</a> to <a href="http://www.mercurial-scm.org" rel="noreferrer" target="_blank">www.mercurial-scm.org</a>)<br>
  (svn.intro.history): s/http/https/ for <a href="http://collab.net" rel="noreferrer" target="_blank">collab.net</a> and <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.intro.whatsnew): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.preface.free): s/http/https/ for <a href="http://svnbook.red-bean.com" rel="noreferrer" target="_blank">svnbook.red-bean.com</a><br>
<br>
* en/book/ch03-advanced-topics.xml<br>
  (svn.advanced.changelists): s/http/https/ for <a href="http://mail.google.com" rel="noreferrer" target="_blank">mail.google.com</a>, <a href="http://www.youtube.com" rel="noreferrer" target="_blank">www.youtube.com</a> and <a href="http://www.flickr.com" rel="noreferrer" target="_blank">www.flickr.com</a><br>
<br>
* en/book/ch04-branching-and-merging.xml<br>
  (svn.branchmerge.basicmerging.reintegrate): s/http/https/ for <a href="http://svnbook.red-bean.com" rel="noreferrer" target="_blank">svnbook.red-bean.com</a><br>
<br>
* en/book/ch06-server-configuration.xml<br>
  (svn.serverconfig.httpd): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.serverconfig.httpd.authn.basic): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.serverconfig.httpd.authn.digest): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.serverconfig.httpd.authz.blanket): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.serverconfig.httpd.ssl.server): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a> and <a href="http://openssl.org" rel="noreferrer" target="_blank">openssl.org</a> (and <a href="http://openssl.org" rel="noreferrer" target="_blank">openssl.org</a> seems to redirect <a href="http://openssl.org" rel="noreferrer" target="_blank">openssl.org</a> to <a href="http://www.openssl.org" rel="noreferrer" target="_blank">www.openssl.org</a>)<br>
  (svn.serverconfig.httpd.extra.browsing.syntax): s/http/https/ <a href="http://viewvc.org" rel="noreferrer" target="_blank">viewvc.org</a>, <a href="http://trac.edgewall.org" rel="noreferrer" target="_blank">trac.edgewall.org</a> and <a href="http://websvnphp.github.io" rel="noreferrer" target="_blank">websvnphp.github.io</a><br>
<br>
* en/book/ch08-embedding-svn.xml<br>
  (svn.developer.usingapi): s/http/https/ for <a href="http://apache.org" rel="noreferrer" target="_blank">apache.org</a><br>
  (svn.developer.usingapi.otherlangs): s/http/https/ for <a href="http://swig.org" rel="noreferrer" target="_blank">swig.org</a> and <a href="http://svnkit.com" rel="noreferrer" target="_blank">svnkit.com</a><br>
<br>
Modified Paths:<br>
--------------<br>
    trunk/en/book/appa-quickstart.xml<br>
    trunk/en/book/appc-webdav.xml<br>
    trunk/en/book/ch00-preface.xml<br>
    trunk/en/book/ch03-advanced-topics.xml<br>
    trunk/en/book/ch04-branching-and-merging.xml<br>
    trunk/en/book/ch06-server-configuration.xml<br>
    trunk/en/book/ch08-embedding-svn.xml<br>
<br>
Modified: trunk/en/book/appa-quickstart.xml<br>
===================================================================<br>
--- trunk/en/book/appa-quickstart.xml   2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/appa-quickstart.xml   2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -46,7 +46,7 @@<br>
<br>
     <para>The easiest way to get Subversion is to download a binary<br>
       package built for your operating system.  Subversion's web site<br>
-      (<ulink url="<a href="http://subversion.apache.org" rel="noreferrer" target="_blank">http://subversion.apache.org</a>"/>) often has these<br>
+      (<ulink url="<a href="https://subversion.apache.org" rel="noreferrer" target="_blank">https://subversion.apache.org</a>"/>) often has these<br>
       packages available for download, posted by volunteers.  The site<br>
       usually contains graphical installer packages for users of<br>
       Microsoft operating systems.  If you run a Unix-like operating<br>
@@ -67,7 +67,7 @@<br>
       Subversion repository in which it lives.  Obviously, you'll need<br>
       to already have a Subversion client on hand to do this.  But<br>
       once you do, you can check out a working copy from<br>
-      <ulink url="<a href="http://svn.apache.org/repos/asf/subversion" rel="noreferrer" target="_blank">http://svn.apache.org/repos/asf/subversion</a>"<br>
+      <ulink url="<a href="https://svn.apache.org/repos/asf/subversion" rel="noreferrer" target="_blank">https://svn.apache.org/repos/asf/subversion</a>"<br>
       /><footnote><para>Note that the URL checked out in the example<br>
       ends not with <literal>subversion</literal>, but with a<br>
       subdirectory thereof called <literal>trunk</literal>.  See our<br>
@@ -76,7 +76,7 @@<br>
<br>
     <informalexample><br>
       <screen><br>
-$ svn checkout <a href="http://svn.apache.org/repos/asf/subversion/trunk" rel="noreferrer" target="_blank">http://svn.apache.org/repos/asf/subversion/trunk</a> subversion<br>
+$ svn checkout <a href="https://svn.apache.org/repos/asf/subversion/trunk" rel="noreferrer" target="_blank">https://svn.apache.org/repos/asf/subversion/trunk</a> subversion<br>
 A    subversion/HACKING<br>
 A    subversion/INSTALL<br>
 A    subversion/README<br>
<br>
Modified: trunk/en/book/appc-webdav.xml<br>
===================================================================<br>
--- trunk/en/book/appc-webdav.xml       2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/appc-webdav.xml       2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -457,7 +457,7 @@<br>
<br>
         <para>DAV Explorer is another standalone WebDAV client, written<br>
           in Java.  It's under a free Apache-like license and is<br>
-          available at <ulink url="<a href="http://www.ics.uci.edu/~webdav/" rel="noreferrer" target="_blank">http://www.ics.uci.edu/~webdav/</a>"/>.<br>
+          available at <ulink url="<a href="https://www.davexplorer.org/" rel="noreferrer" target="_blank">https://www.davexplorer.org/</a>"/>.<br>
           It does everything cadaver does, but has the<br>
           advantages of being portable and being a more user-friendly GUI<br>
           application.  It's also one of the first clients to support<br>
@@ -576,9 +576,9 @@<br>
         <title>Nautilus, Konqueror</title><br>
<br>
         <para>Nautilus is the official file manager/browser for the<br>
-          GNOME desktop (<ulink url="<a href="http://www.gnome.org" rel="noreferrer" target="_blank">http://www.gnome.org</a>"/>), and<br>
+          GNOME desktop (<ulink url="<a href="https://www.gnome.org" rel="noreferrer" target="_blank">https://www.gnome.org</a>"/>), and<br>
           Konqueror is the manager/browser for the KDE desktop (<ulink<br>
-          url="<a href="http://www.kde.org" rel="noreferrer" target="_blank">http://www.kde.org</a>"/>).  Both of these applications<br>
+          url="<a href="https://kde.org" rel="noreferrer" target="_blank">https://kde.org</a>"/>).  Both of these applications<br>
           have an explorer-level WebDAV client built in, and they<br>
           operate just fine against an autoversioning repository.</para><br>
<br>
@@ -626,7 +626,7 @@<br>
           contents of these WebDAV-backed pseudodrives as easily as<br>
           you can against real local hard drives, and in the same<br>
           ways.  You can purchase WebDrive from South River<br>
-          Technologies (<ulink url="<a href="http://www.southrivertech.com" rel="noreferrer" target="_blank">http://www.southrivertech.com</a>"/>).<br>
+          Technologies (<ulink url="<a href="https://southrivertech.com" rel="noreferrer" target="_blank">https://southrivertech.com</a>"/>).<br>
           Novell's NetDrive is freely available online, but requires<br>
           users to have a NetWare license.</para><br>
<br>
@@ -679,7 +679,7 @@<br>
<br>
         <para>Linux davfs2 is a filesystem module for the Linux<br>
           kernel, whose development is organized at<br>
-         <ulink url="<a href="http://savannah.nongnu.org/projects/davfs2" rel="noreferrer" target="_blank">http://savannah.nongnu.org/projects/davfs2</a>"/>.  Once you<br>
+         <ulink url="<a href="https://savannah.nongnu.org/projects/davfs2" rel="noreferrer" target="_blank">https://savannah.nongnu.org/projects/davfs2</a>"/>.  Once you<br>
           install davfs2, you can mount a WebDAV network share using<br>
           the usual Linux mount command:</para><br>
<br>
<br>
Modified: trunk/en/book/ch00-preface.xml<br>
===================================================================<br>
--- trunk/en/book/ch00-preface.xml      2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/ch00-preface.xml      2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -191,8 +191,8 @@<br>
         methodology of version control called <firstterm>distributed<br>
         version control</firstterm> has likewise garnered widespread<br>
         attention and adoption.  Tools such as Git<br>
-        (<ulink url="<a href="http://git-scm.com/" rel="noreferrer" target="_blank">http://git-scm.com/</a>" />) and Mercurial<br>
-        (<ulink url="<a href="http://mercurial-scm.org/" rel="noreferrer" target="_blank">http://mercurial-scm.org/</a>" />) have risen<br>
+        (<ulink url="<a href="https://git-scm.com/" rel="noreferrer" target="_blank">https://git-scm.com/</a>" />) and Mercurial<br>
+        (<ulink url="<a href="https://www.mercurial-scm.org/" rel="noreferrer" target="_blank">https://www.mercurial-scm.org/</a>" />) have risen<br>
         to the tops of the distributed version control system (DVCS)<br>
         ranks.  Distributed version control harnesses the growing<br>
         ubiquity of high-speed network connections and low storage<br>
@@ -253,7 +253,7 @@<br>
         <indexterm><br>
           <primary>CollabNet</primary><br>
         </indexterm>In early 2000, CollabNet,<br>
-        Inc. (<ulink url="<a href="http://www.collab.net" rel="noreferrer" target="_blank">http://www.collab.net</a>"/>) began seeking<br>
+        Inc. (<ulink url="<a href="https://www.collab.net" rel="noreferrer" target="_blank">https://www.collab.net</a>"/>) began seeking<br>
         developers to write a replacement for CVS.  CollabNet<br>
         offered<footnote><para>CollabNet Enterprise Edition has since<br>
         been replaced by a new product line called CollabNet<br>
@@ -326,7 +326,7 @@<br>
         Subversion contributors.  In early 2010, Subversion was fully<br>
         adopted into the ASF's family of top-level projects, moved its<br>
         web presence to<br>
-        <ulink url="<a href="http://subversion.apache.org" rel="noreferrer" target="_blank">http://subversion.apache.org</a>"/>, and was<br>
+        <ulink url="<a href="https://subversion.apache.org" rel="noreferrer" target="_blank">https://subversion.apache.org</a>"/>, and was<br>
         rechristened <quote>Apache Subversion</quote>.</para><br>
<br>
     </sect2><br>
@@ -510,7 +510,7 @@<br>
         summary of major new changes since Subversion 1.0.  Note that<br>
         this is not a complete list; for full details, please visit<br>
         Subversion's web site at<br>
-        <ulink url="<a href="http://subversion.apache.org" rel="noreferrer" target="_blank">http://subversion.apache.org</a>"/>.</para><br>
+        <ulink url="<a href="https://subversion.apache.org" rel="noreferrer" target="_blank">https://subversion.apache.org</a>"/>.</para><br>
<br>
       <variablelist><br>
<br>
@@ -973,7 +973,7 @@<br>
<br>
     <para>The online home of this book's development and most of the<br>
       volunteer-driven translation efforts regarding it is<br>
-      <ulink url="<a href="http://svnbook.red-bean.com" rel="noreferrer" target="_blank">http://svnbook.red-bean.com</a>"/>.  There you can find<br>
+      <ulink url="<a href="https://svnbook.red-bean.com" rel="noreferrer" target="_blank">https://svnbook.red-bean.com</a>"/>.  There you can find<br>
       links to the latest releases and tagged versions of the book in<br>
       various formats, as well as instructions for accessing the<br>
       book's Subversion repository (where its DocBook XML source<br>
<br>
Modified: trunk/en/book/ch03-advanced-topics.xml<br>
===================================================================<br>
--- trunk/en/book/ch03-advanced-topics.xml      2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/ch03-advanced-topics.xml      2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -5248,7 +5248,7 @@<br>
       applied to working copy files for the express purpose of<br>
       associating multiple files together.  Users of many of Google's<br>
       software offerings are familiar with this concept already.  For<br>
-      example, <ulink url="<a href="http://mail.google.com/" rel="noreferrer" target="_blank">http://mail.google.com/</a>">Gmail</ulink><br>
+      example, <ulink url="<a href="https://mail.google.com/" rel="noreferrer" target="_blank">https://mail.google.com/</a>">Gmail</ulink><br>
       doesn't provide the traditional folders-based email organization<br>
       mechanism.  In Gmail, you apply arbitrary labels to emails, and<br>
       multiple emails can be said to be part of the same group if they<br>
@@ -5256,8 +5256,8 @@<br>
       similarly labeled emails then becomes a simple user interface<br>
       trick.  Many other Web 2.0 sites have similar<br>
       mechanisms&mdash;consider the <quote>tags</quote> used by sites<br>
-      such as <ulink url="<a href="http://www.youtube.com/" rel="noreferrer" target="_blank">http://www.youtube.com/</a>">YouTube</ulink> and<br>
-      <ulink url="<a href="http://www.flickr.com/" rel="noreferrer" target="_blank">http://www.flickr.com/</a>">Flickr</ulink>,<br>
+      such as <ulink url="<a href="https://www.youtube.com/" rel="noreferrer" target="_blank">https://www.youtube.com/</a>">YouTube</ulink> and<br>
+      <ulink url="<a href="https://www.flickr.com/" rel="noreferrer" target="_blank">https://www.flickr.com/</a>">Flickr</ulink>,<br>
       <quote>categories</quote> applied to blog posts, and so on.<br>
       Folks understand today that organization of data is critical,<br>
       but that how that data is organized needs to be a flexible<br>
<br>
Modified: trunk/en/book/ch04-branching-and-merging.xml<br>
===================================================================<br>
--- trunk/en/book/ch04-branching-and-merging.xml        2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/ch04-branching-and-merging.xml        2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -1277,7 +1277,7 @@<br>
         versions require some special handling before a feature branch<br>
         can be reintegrated more than once.  See the earlier version of<br>
         this chapter for more information: <ulink<br>
-        url="<a href="http://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate" rel="noreferrer" target="_blank">http://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate</a>"<br>
+        url="<a href="https://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate" rel="noreferrer" target="_blank">https://svnbook.red-bean.com/en/1.7/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate</a>"<br>
         /></para></footnote>. If you do this, only the changes made on your<br>
         branch after the first reintegrate are merged to the trunk.</para><br>
     </sect2><br>
<br>
Modified: trunk/en/book/ch06-server-configuration.xml<br>
===================================================================<br>
--- trunk/en/book/ch06-server-configuration.xml 2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/ch06-server-configuration.xml 2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -2008,9 +2008,9 @@<br>
       of the use of these directives, describing them in full is<br>
       outside the scope of this chapter.  The Apache team maintains<br>
       excellent documentation, publicly available on their web site at<br>
-      <ulink url="<a href="http://httpd.apache.org" rel="noreferrer" target="_blank">http://httpd.apache.org</a>"/>.  For example, a general<br>
+      <ulink url="<a href="https://httpd.apache.org" rel="noreferrer" target="_blank">https://httpd.apache.org</a>"/>.  For example, a general<br>
       reference for the configuration directives is located at<br>
-      <ulink url="<a href="http://httpd.apache.org/docs/current/mod/directives.html" rel="noreferrer" target="_blank">http://httpd.apache.org/docs/current/mod/directives.html</a>"<br>
+      <ulink url="<a href="https://httpd.apache.org/docs/current/mod/directives.html" rel="noreferrer" target="_blank">https://httpd.apache.org/docs/current/mod/directives.html</a>"<br>
       />.</para><br>
<br>
     <para>Also, as you make changes to your Apache setup, it is likely<br>
@@ -2317,7 +2317,7 @@<br>
           Basic authentication mechanism, which simply uses a username<br>
           and password to verify a user's identity.  Apache provides<br>
           the <command>htpasswd</command> utility<footnote><para>See<br>
-          <ulink url="<a href="http://httpd.apache.org/docs/current/programs/htpasswd.html" rel="noreferrer" target="_blank">http://httpd.apache.org/docs/current/programs/htpasswd.html</a>"<br>
+          <ulink url="<a href="https://httpd.apache.org/docs/current/programs/htpasswd.html" rel="noreferrer" target="_blank">https://httpd.apache.org/docs/current/programs/htpasswd.html</a>"<br>
           />.</para></footnote> for managing files containing<br>
           usernames and passwords.</para><br>
<br>
@@ -2502,7 +2502,7 @@<br>
           uses a different file format than Basic authentication, <br>
           created and managed using Apache's <command>htdigest</command><br>
           utility<footnote><para>See<br>
-          <ulink url="<a href="http://httpd.apache.org/docs/current/programs/htdigest.html" rel="noreferrer" target="_blank">http://httpd.apache.org/docs/current/programs/htdigest.html</a>"<br>
+          <ulink url="<a href="https://httpd.apache.org/docs/current/programs/htdigest.html" rel="noreferrer" target="_blank">https://httpd.apache.org/docs/current/programs/htdigest.html</a>"<br>
           />.</para></footnote> rather than <command>htpasswd</command>.<br>
           Digest authentication also has the additional concept of a<br>
           <quote>realm</quote>, which must match the value of the<br>
@@ -2634,7 +2634,7 @@<br>
           <literal>Require</literal> directive, take a look at the<br>
           <literal>Security</literal> section of the Apache<br>
           documentation's tutorials collection at <ulink<br>
-          url="<a href="http://httpd.apache.org/docs-2.0/misc/tutorials.html" rel="noreferrer" target="_blank">http://httpd.apache.org/docs-2.0/misc/tutorials.html</a>"/>.</para><br>
+          url="<a href="https://httpd.apache.org/docs-2.0/misc/tutorials.html" rel="noreferrer" target="_blank">https://httpd.apache.org/docs-2.0/misc/tutorials.html</a>"/>.</para><br>
<br>
       </sect3><br>
<br>
@@ -2922,7 +2922,7 @@<br>
           generate client and server SSL certificates and how to<br>
           configure Apache to use them.  Many other references,<br>
           including Apache's own documentation (<ulink <br>
-          url="<a href="http://httpd.apache.org/docs/current/ssl/" rel="noreferrer" target="_blank">http://httpd.apache.org/docs/current/ssl/</a>"/>),<br>
+          url="<a href="https://httpd.apache.org/docs/current/ssl/" rel="noreferrer" target="_blank">https://httpd.apache.org/docs/current/ssl/</a>"/>),<br>
           describe the process.</para><br>
<br>
         <tip><br>
@@ -2929,7 +2929,7 @@<br>
           <para>SSL certificates from well-known entities generally<br>
             cost money, but at a bare minimum, you can configure<br>
             Apache to use a self-signed certificate generated with a<br>
-            tool such as OpenSSL (<ulink url="<a href="http://openssl.org" rel="noreferrer" target="_blank">http://openssl.org</a>"<br>
+            tool such as OpenSSL (<ulink url="<a href="https://www.openssl.org" rel="noreferrer" target="_blank">https://www.openssl.org</a>"<br>
             />).<footnote><para>While self-signed certificates are<br>
             still vulnerable to a <quote>man-in-the-middle</quote><br>
             attack (before a client sees the certificate for the first<br>
@@ -3347,9 +3347,9 @@<br>
             properties.  For folks who require more extensive browsing<br>
             of repositories and their history, there are several<br>
             third-party software packages which offer this.  Some<br>
-            examples include ViewVC (<ulink url="<a href="http://viewvc.org" rel="noreferrer" target="_blank">http://viewvc.org</a>" />),<br>
-            Trac (<ulink url="<a href="http://trac.edgewall.org" rel="noreferrer" target="_blank">http://trac.edgewall.org</a>" />) and WebSVN<br>
-            (<ulink url="<a href="http://websvnphp.github.io" rel="noreferrer" target="_blank">http://websvnphp.github.io</a>" />).  These third-party<br>
+            examples include ViewVC (<ulink url="<a href="https://viewvc.org" rel="noreferrer" target="_blank">https://viewvc.org</a>" />),<br>
+            Trac (<ulink url="<a href="https://trac.edgewall.org" rel="noreferrer" target="_blank">https://trac.edgewall.org</a>" />) and WebSVN<br>
+            (<ulink url="<a href="https://websvnphp.github.io" rel="noreferrer" target="_blank">https://websvnphp.github.io</a>" />).  These third-party<br>
             tools don't affect <command>mod_dav_svn</command>'s<br>
             built-in <quote>browseability</quote>, and generally offer<br>
             a much wider set of features, including the display of the<br>
<br>
Modified: trunk/en/book/ch08-embedding-svn.xml<br>
===================================================================<br>
--- trunk/en/book/ch08-embedding-svn.xml        2022-08-18 09:07:57 UTC (rev 6056)<br>
+++ trunk/en/book/ch08-embedding-svn.xml        2022-08-19 06:28:42 UTC (rev 6057)<br>
@@ -658,7 +658,7 @@<br>
     <para>Another good source of information about programming against<br>
       the Subversion APIs is the project's own hacking guidelines,<br>
       which you can find at<br>
-      <ulink url="<a href="http://subversion.apache.org/docs/community-guide/" rel="noreferrer" target="_blank">http://subversion.apache.org/docs/community-guide/</a>"<br>
+      <ulink url="<a href="https://subversion.apache.org/docs/community-guide/" rel="noreferrer" target="_blank">https://subversion.apache.org/docs/community-guide/</a>"<br>
       />.  This document contains useful information, which, while<br>
       aimed at developers and would-be developers of Subversion<br>
       itself, is equally applicable to folks developing against<br>
@@ -841,7 +841,7 @@<br>
         compensate for complex APIs that SWIG needs some help<br>
         translating between languages.  For more information on SWIG<br>
         itself, see the project's web site at <ulink<br>
-        url="<a href="http://www.swig.org/" rel="noreferrer" target="_blank">http://www.swig.org/</a>"/>.</para><br>
+        url="<a href="https://www.swig.org/" rel="noreferrer" target="_blank">https://www.swig.org/</a>"/>.</para><br>
<br>
       <para>Subversion also has language bindings for Java.  The<br>
         javahl bindings (located in<br>
@@ -871,7 +871,7 @@<br>
         interface than the more C-like APIs provided by Subversion's<br>
         own Python bindings.  And if you're looking for a pure Java<br>
         implementation of Subversion, check out SVNKit (<ulink<br>
-        url="<a href="http://svnkit.com/" rel="noreferrer" target="_blank">http://svnkit.com/</a>" />), which is Subversion rewritten<br>
+        url="<a href="https://svnkit.com/" rel="noreferrer" target="_blank">https://svnkit.com/</a>" />), which is Subversion rewritten<br>
         from the ground up in Java.</para><br>
<br>
       <sidebar><br>
@@ -880,7 +880,7 @@<br>
         <para>In 2005, a small company called TMate announced the<br>
           1.0.0 release of JavaSVN&mdash;a pure Java implementation of<br>
           Subversion.  Since then, the project has been renamed to<br>
-          SVNKit (available at <ulink url="<a href="http://svnkit.com/" rel="noreferrer" target="_blank">http://svnkit.com/</a>" />)<br>
+          SVNKit (available at <ulink url="<a href="https://svnkit.com/" rel="noreferrer" target="_blank">https://svnkit.com/</a>" />)<br>
           and has seen great success as a provider of Subversion<br>
           functionality to various Subversion clients, IDE<br>
           integrations, and other third-party tools.</para><br>
@@ -899,7 +899,7 @@<br>
           be accompanied by information on how to obtain complete<br>
           source code for the software that uses SVNKit and any<br>
           accompanying software that uses the software that uses<br>
-          SVNKit. See <ulink url="<a href="http://svnkit.com/license.html" rel="noreferrer" target="_blank">http://svnkit.com/license.html</a>" /><br>
+          SVNKit. See <ulink url="<a href="https://svnkit.com/license.html" rel="noreferrer" target="_blank">https://svnkit.com/license.html</a>" /><br>
           for details.</para></footnote>  Finally, by aiming to be a<br>
           pure Java Subversion library, SVNKit is limited in which<br>
           portions of Subversion can be reasonably cloned while still<br>
<br>
<br>
</blockquote></div>