changeset 358:011b01ccf52d

fixing external hyperlinks
author Sebastien Jodogne <s.jodogne@gmail.com>
date Mon, 30 Mar 2020 18:47:35 +0200
parents 6b432ce3a56e
children 9acb9354da1a
files Sphinx/source/conf.py Sphinx/source/contributing.rst Sphinx/source/developers/creating-plugins.rst Sphinx/source/developers/db-versioning.rst Sphinx/source/developers/stone.rst Sphinx/source/dicom-guide.rst Sphinx/source/faq/compiling-old.rst Sphinx/source/faq/crash.rst Sphinx/source/faq/debugging.rst Sphinx/source/faq/dicom.rst Sphinx/source/faq/https.rst Sphinx/source/faq/improving-interface.rst Sphinx/source/faq/licensing.rst Sphinx/source/faq/log.rst Sphinx/source/faq/matlab.rst Sphinx/source/faq/proprietary.rst Sphinx/source/faq/supported-images.rst Sphinx/source/faq/troubleshooting.rst Sphinx/source/faq/video.rst Sphinx/source/faq/viewers.rst Sphinx/source/faq/why-orthanc.rst Sphinx/source/faq/worklist.rst Sphinx/source/index.rst Sphinx/source/plugins.rst Sphinx/source/plugins/dicomweb.rst Sphinx/source/plugins/google-cloud-platform.rst Sphinx/source/plugins/mysql.rst Sphinx/source/plugins/osimis-webviewer.rst Sphinx/source/plugins/postgresql.rst Sphinx/source/plugins/transfers.rst Sphinx/source/plugins/webviewer.rst Sphinx/source/plugins/worklists-plugin.rst Sphinx/source/plugins/wsi.rst Sphinx/source/users/backup.rst Sphinx/source/users/cookbook.rst Sphinx/source/users/docker.rst Sphinx/source/users/lua.rst Sphinx/source/users/replication.rst Sphinx/source/users/rest.rst Sphinx/source/users/storage-commitment.rst
diffstat 40 files changed, 162 insertions(+), 156 deletions(-) [+]
line wrap: on
line diff
--- a/Sphinx/source/conf.py	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/conf.py	Mon Mar 30 18:47:35 2020 +0200
@@ -295,3 +295,8 @@
 
 # If true, do not generate a @detailmenu in the "Top" node's menu.
 #texinfo_no_detailmenu = False
+
+
+linkcheck_timeout=3
+linkcheck_retries=2
+linkcheck_workers=15
--- a/Sphinx/source/contributing.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/contributing.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -13,7 +13,7 @@
     on `Facebook <https://www.facebook.com/orthancdicom/>`__ and
     `Twitter <https://twitter.com/OrthancServer>`__).
   - Answer our `survey
-    <http://www.orthanc-server.com/static.php?page=blog#survey>`_.
+    <https://www.orthanc-server.com/static.php?page=blog#survey>`_.
   - Improve and translate the `Wikipedia pages
     <https://en.wikipedia.org/wiki/Orthanc_(software)>`_ about Orthanc.
   - Cite the `reference paper about Orthanc
@@ -49,7 +49,7 @@
     :ref:`dedicated FAQ entry <cla>`.
   - Interface Orthanc with other software (e.g. 3D Slicer,
     Matlab/Octave, Python, Horos, dicompyler...). Check the `already
-    supported frameworks <http://www.orthanc-server.com/static.php?page=resources>`_.
+    supported frameworks <https://www.orthanc-server.com/static.php?page=resources>`_.
   - Develop :ref:`C/C++ plugins extending the Orthanc core <plugins>`.  Here are some ideas
     of possible plugins:
   
--- a/Sphinx/source/developers/creating-plugins.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/developers/creating-plugins.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -13,7 +13,7 @@
 <plugins>`.
 
 Orthanc plugins must use the `plugin SDK
-<http://sdk.orthanc-server.com/>`__ and must be written in C or
+<https://sdk.orthanc-server.com/>`__ and must be written in C or
 C++. They must also fullfil the terms of the `GPLv3 license
 <http://www.gnu.org/licenses/quick-guide-gplv3.en.html>`__ that is
 used by the core of Orthanc. Here are some resources about creating
@@ -26,10 +26,10 @@
 
 * A tutorial showing how to implement a basic WADO server is
   `available on CodeProject
-  <http://www.codeproject.com/Articles/797118/Implementing-a-WADO-Server-using-Orthanc>`__.
+  <https://www.codeproject.com/Articles/797118/Implementing-a-WADO-Server-using-Orthanc>`__.
 
 * Marco Barnig provides `tutorial lessons to create Orthanc plugins
-  <https://github.com/mbarnig/RadioLogic/wiki#orthanc-plugin-development>`__
+  <https://github.com/mbarnig/RadioLogic/wiki#user-content-orthanc-plugin-development>`__
   as part of his `RadioLogic project
   <https://github.com/mbarnig/RadioLogic/>`__.
   
@@ -37,7 +37,7 @@
 core <coding-style>`, although this is of course not required.
 
 Do not hesitate to `contact us
-<http://www.orthanc-server.com/static.php?page=contact>`__ if you wish
+<https://www.orthanc-server.com/static.php?page=contact>`__ if you wish
 your plugin to be **indexed** in :ref:`the dedicated part of the
 Orthanc Book <plugins-contributed>`!
 
@@ -75,7 +75,7 @@
 * `Plugins/Include/orthanc/OrthancCPlugin.h
   <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Include/orthanc/OrthancCPlugin.h>`__
 
-`Online documentation <http://sdk.orthanc-server.com/>`__ for this C
+`Online documentation <https://sdk.orthanc-server.com/>`__ for this C
 header is available, as generated by `Doxygen
 <https://en.wikipedia.org/wiki/Doxygen>`__.
 
--- a/Sphinx/source/developers/db-versioning.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/developers/db-versioning.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -4,10 +4,10 @@
 ===================
 
 Orthanc stores the index of the DICOM instances as an embedded `SQLite
-database <http://www.sqlite.org/>`_. The schema of this database has
-evolved across the versions of Orthanc, making the database
-incompatible between versions. This page clarifies which versions of
-Orthanc are compatible with other versions.
+database <https://www.sqlite.org/index.html>`_. The schema of this
+database has evolved across the versions of Orthanc, making the
+database incompatible between versions. This page clarifies which
+versions of Orthanc are compatible with other versions.
 
 Recent versions (post-0.3.1)
 ----------------------------
--- a/Sphinx/source/developers/stone.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/developers/stone.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -4,7 +4,7 @@
 ================
 
 This section of the Orthanc Book will document `Stone of Orthanc
-<http://www.orthanc-server.com/static.php?page=stone>`__. This is
+<https://www.orthanc-server.com/static.php?page=stone>`__. This is
 work-in-progress.
 
 For the time being, documentation is provided through various sample
--- a/Sphinx/source/dicom-guide.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/dicom-guide.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -7,18 +7,18 @@
 
 
 This section of the Orthanc Book provides a **gentle, informal,
-high-level introduction to DICOM**. We will try and map
-DICOM's own concepts to a modern terminology that should hopefully be
-more easy to understand for software engineers diving for the first
-time into DICOM. Once the concepts of this page are understood,
-interested readers are invited to read a more formal textbook about
-DICOM, such as the so-called "`Practical introduction and survival
-guide <http://www.springer.com/us/book/9783642108495>`__", or to read
-the full `DICOM specification
+high-level introduction to DICOM**. We will try and map DICOM's own
+concepts to a modern terminology that should hopefully be more easy to
+understand for software engineers diving for the first time into
+DICOM. Once the concepts of this page are understood, interested
+readers are invited to read a more formal textbook about DICOM, such
+as the so-called "`Practical introduction and survival guide
+<https://www.springer.com/us/book/9783642108495>`__", or to read the
+full `DICOM specification
 <http://dicom.nema.org/medical/dicom/current/output/html/>`__.
 
 All the DICOM concepts that are defined in this introduction are
-illustrated with `Orthanc <http://www.orthanc-server.com/>`__, a
+illustrated with `Orthanc <https://www.orthanc-server.com/>`__, a
 lightweight, yet powerful standalone DICOM server for healthcare and
 medical research. As Orthanc is free and open-source software, it is a
 good companion to learn DICOM.
@@ -617,11 +617,12 @@
    authentication and :ref:`SSL encryption <https>`. The :ref:`Orthanc
    Explorer <orthanc-explorer>` interface can transparently use this
    peer mechanism to send DICOM files over HTTP(S).
-2. Resort to the `DICOMweb standard <http://www.dicomweb.org/>`__,
-   that is an extension to the DICOM standard specifying how to access
-   the content of a remote DICOM server through HTTP(S). Because the
-   peer mechanism is bound to Orthanc, DICOMweb offers a less
-   expressive, but more generic access to remote servers.
-   Importantly, a `DICOMweb plugin to Orthanc
-   <http://www.orthanc-server.com/static.php?page=dicomweb>`__ is
+2. Resort to the `DICOMweb standard
+   <https://www.dicomstandard.org/dicomweb/>`__, that is an extension
+   to the DICOM standard specifying how to access the content of a
+   remote DICOM server through HTTP(S). Because the peer mechanism is
+   bound to Orthanc, DICOMweb offers a less expressive, but more
+   generic access to remote servers.  Importantly, a `DICOMweb plugin
+   to Orthanc
+   <https://www.orthanc-server.com/static.php?page=dicomweb>`__ is
    freely available.
--- a/Sphinx/source/faq/compiling-old.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/compiling-old.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -61,7 +61,7 @@
     $ cmake -DSTATIC_BUILD:BOOL=OFF -DSTANDALONE_BUILD:BOOL=ON -DUSE_DYNAMIC_JSONCPP:BOOL=ON -DDEBIAN_USE_GTEST_SOURCE_PACKAGE:BOOL=ON -DCMAKE_BUILD_TYPE=Debug -DDCMTK_LIBRARIES="wrap;oflog"
 
 This is the configuration from the `official Debian package
-<http://anonscm.debian.org/cgit/debian-med/orthanc.git/tree/debian/orthanc.init>`_.
+<https://salsa.debian.org/med-team/orthanc/-/blob/master/debian/orthanc.init>`_.
 
 Dynamic Linking on Fedora 18 and 19
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -71,15 +71,14 @@
     $ cmake -DSTATIC_BUILD:BOOL=OFF -DSTANDALONE_BUILD:BOOL=ON -DUSE_DYNAMIC_GOOGLE_LOG:BOOL=ON -DUSE_DYNAMIC_JSONCPP:BOOL=ON -DCMAKE_BUILD_TYPE=Debug
 
 This is the configuration from the `official Fedora package
-<http://pkgs.fedoraproject.org/cgit/orthanc.git/tree/orthanc.spec?h=f18>`_.
+<https://src.fedoraproject.org/rpms/orthanc/blob/master/f/orthanc.spec>`_.
 
 Static Linking on CentOS 6.3 and 6.4
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 You have to build and install `CMake 2.8 from source
-<https://cmake.org/download/>`_, or you can use
-the cmake28 package from `EPEL
-<https://admin.fedoraproject.org/pkgdb/package/rpms/cmake28/>`_. The
+<https://cmake.org/download/>`_, or you can use the cmake28 package
+from `EPEL <https://src.fedoraproject.org/rpms/cmake28>`_. The
 ``STATIC_BUILD=ON`` option will then work::
 
     $ /usr/local/bin/cmake -DSTATIC_BUILD:BOOL=ON -DCMAKE_BUILD_TYPE=Debug
--- a/Sphinx/source/faq/crash.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/crash.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -64,7 +64,7 @@
 above <segfault-plugin>` is available as the ``crash.cpp`` file, here
 is a sample debug session::
 
-  $ wget http://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc
+  $ wget https://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc
   $ chmod +x ./Orthanc
   $ gcc -fPIC -shared ./crash.cpp -I ~/orthanc/Plugins/Include -o crash.so
   $ ulimit -c unlimited
--- a/Sphinx/source/faq/debugging.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/debugging.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -45,7 +45,7 @@
 to debug Orthanc without compiling from sources. Here is a sample
 debug session::
 
-  $ wget http://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc
+  $ wget https://lsb.orthanc-server.com/orthanc/debug/1.6.0/Orthanc
   $ chmod +x ./Orthanc
   $ gdb ./Orthanc Configuration.json
   (gdb) catch throw
@@ -67,13 +67,13 @@
 plugins precompiled using the LSB are also available at the following
 locations:
 
-* `Orthanc core <http://lsb.orthanc-server.com/orthanc/debug/>`__
-* `DICOMweb plugin <http://lsb.orthanc-server.com/plugin-dicom-web/debug/>`__
-* `MySQL plugin <http://lsb.orthanc-server.com/plugin-mysql/debug/>`__
-* `Orthanc Web viewer <http://lsb.orthanc-server.com/plugin-webviewer/debug/>`__
-* `PostgreSQL plugin <http://lsb.orthanc-server.com/plugin-postgresql/debug/>`__
-* `Transfers accelerator plugin <http://lsb.orthanc-server.com/plugin-transfers/debug/>`__
-* `Whole-slide imaging <http://lsb.orthanc-server.com/whole-slide-imaging/debug/>`__
+* `Orthanc core <https://lsb.orthanc-server.com/orthanc/debug/>`__
+* `DICOMweb plugin <https://lsb.orthanc-server.com/plugin-dicom-web/debug/>`__
+* `MySQL plugin <https://lsb.orthanc-server.com/plugin-mysql/debug/>`__
+* `Orthanc Web viewer <https://lsb.orthanc-server.com/plugin-webviewer/debug/>`__
+* `PostgreSQL plugin <https://lsb.orthanc-server.com/plugin-postgresql/debug/>`__
+* `Transfers accelerator plugin <https://lsb.orthanc-server.com/plugin-transfers/debug/>`__
+* `Whole-slide imaging <https://lsb.orthanc-server.com/whole-slide-imaging/debug/>`__
   
 
 Docker
--- a/Sphinx/source/faq/dicom.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/dicom.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -7,7 +7,7 @@
 computer network are related to the configuration of these
 modalities. As preliminary debugging actions, you should:
 
-* Make sure you use the `most recent version <http://www.orthanc-server.com/download.php>`_ of Orthanc.
+* Make sure you use the `most recent version <https://www.orthanc-server.com/download.php>`_ of Orthanc.
 * Make sure the two computers can "ping" each other.
 * Turn off all the firewalls on the two computers (especially on Microsoft Windows).
 * Make sure the remote computer has `DICOM TLS encryption
--- a/Sphinx/source/faq/https.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/https.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -40,6 +40,6 @@
 
 Some interesting references about this topic can be found `here
 <http://www.devsec.org/info/ssl-cert.html>`__, `here
-<http://www.akadia.com/services/ssh_test_certificate.html>`__, and
+<https://www.akadia.com/services/ssh_test_certificate.html>`__, and
 `here
-<http://stackoverflow.com/questions/991758/how-to-get-an-openssl-pem-file-from-key-and-crt-files>`__.
+<https://stackoverflow.com/questions/991758/how-to-get-pem-file-from-key-and-crt-files>`__.
--- a/Sphinx/source/faq/improving-interface.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/improving-interface.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -43,10 +43,10 @@
 funding for this development). In the meantime, you can also contact a
 company that provides **commercial support on the top of Orthanc** and
 that might have developed an advanced user interface. Currently,
-`Osimis <http://osimis.io/>`_ is the only company ensuring such
+`Osimis <https://www.osimis.io/>`_ is the only company ensuring such
 corporate services, but others might show up in the future. A `contact
-form <http://www.orthanc-server.com/orthanc-pro.php>`_ is available on
-the official Web page of Orthanc.
+form <https://www.orthanc-server.com/orthanc-pro.php>`_ is available
+on the official Web page of Orthanc.
 
 **Update (2017-10-03):** A team of Master students from `ULiège
 <https://www.uliege.be/>`__ is currently working on creating a
--- a/Sphinx/source/faq/licensing.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/licensing.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -92,7 +92,7 @@
 | is hosted by an Orthanc server where some           |               |       |        |              |                        |                   |
 | AGPL-licensed plugin is installed                   |               |       |        |              |                        |                   |
 +-----------------------------------------------------+---------------+-------+--------+--------------+------------------------+-------------------+
-| Creating a :ref:`Python script <python>`            | No            | No    | Yes    | Yes          | Dual licensing         | Dual licensing    |
+| Creating a :ref:`Python script <python-plugin>`     | No            | No    | Yes    | Yes          | Dual licensing         | Dual licensing    |
 +-----------------------------------------------------+---------------+-------+--------+--------------+------------------------+-------------------+
 | Using a modified version of the GPL-licensed        | No            | Yes   | Yes    | Yes          | Dual licensing         | Yes               |
 | code of Orthanc, or using a modified version of     |               |       |        |              |                        |                   |
@@ -115,9 +115,9 @@
   its global architecture.
 
 * If your use case falls in a "**Dual licensing**" cell, please get in
-  touch with `Osimis <http://osimis.io/>`__, the commercial partner of
-  the Orthanc project that is the only entity entitled to grant a
-  `license exception
+  touch with `Osimis <https://www.osimis.io/>`__, the commercial
+  partner of the Orthanc project that is the only entity entitled to
+  grant a `license exception
   <https://www.fsf.org/blogs/rms/selling-exceptions>`__ to your
   company for the Orthanc core and its :ref:`associated official
   plugins <plugins-official>`.
@@ -148,7 +148,7 @@
   sells **CE-approved** versions of a Web viewer plugin.
 
 * You are kindly invited to cite the `reference paper about Orthanc
-  <https://link.springer.com/article/10.1007%2Fs10278-018-0082-y>`__
+  <https://link.springer.com/article/10.1007/s10278-018-0082-y>`__
   in your scientific work.
 
 * This is our own simplified, technical interpretation of the GPLv3+
@@ -278,7 +278,7 @@
 
 * Unit testing is mandatory. Integration tests should be submitted to
   the `dedicated repository
-  <http://bitbucket.org/sjodogne/orthanc-tests/>`__.
+  <https://bitbucket.org/sjodogne/orthanc-tests/>`__.
 
 * In the case of a doubt wrt. a potential contribution, please discuss
   it on the `Orthanc Users
--- a/Sphinx/source/faq/log.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/log.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -44,7 +44,7 @@
 Under Windows, if you used the official installer:
 
 1. Download the `precompiled command-line version
-   <http://www.orthanc-server.com/download-windows.php>`__ of Orthanc.
+   <https://www.orthanc-server.com/download-windows.php>`__ of Orthanc.
 
 2. Stop the Orthanc service. The actual process depends on your
    version of Windows.
--- a/Sphinx/source/faq/matlab.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/matlab.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -12,7 +12,7 @@
 
 Both Matlab and Octave have access to HTTP servers thanks to their
 built-in `urlread() function
-<http://nl.mathworks.com/help/matlab/ref/urlread.html>`__.  Once must
+<https://nl.mathworks.com/help/matlab/ref/urlread.html>`__.  Once must
 simply install a Matlab/Octave library to decode JSON files.  The
 `JSONLab toolkit <https://github.com/fangq/jsonlab>`__ works perfectly
 to this end.
--- a/Sphinx/source/faq/proprietary.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/proprietary.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -49,7 +49,7 @@
 Finally, if you need to complement the commercial services of your
 official supplier, please note that you can also contact a company
 that provides **commercial support on the top of Orthanc**. Currently,
-`Osimis <http://osimis.io/>`_ is the only company ensuring such
+`Osimis <https://www.osimis.io/>`_ is the only company ensuring such
 corporate services, but others might show up in the future. A `contact
-form <http://www.orthanc-server.com/orthanc-pro.php>`_ is available on
-the official Web page of Orthanc.
+form <https://www.orthanc-server.com/orthanc-pro.php>`_ is available
+on the official Web page of Orthanc.
--- a/Sphinx/source/faq/supported-images.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/supported-images.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -32,7 +32,7 @@
 also be displayed from Orthanc Explorer.
 
 Other type of encodings are available in the `Web viewer plugin
-<http://www.orthanc-server.com/static.php?page=web-viewer>`__, that
+<https://www.orthanc-server.com/static.php?page=web-viewer>`__, that
 mostly supports whatever is supported by the well-known `GDCM toolkit
 <https://sourceforge.net/projects/gdcm/>`__ by Mathieu Malaterre. Note
 however that multiframe (notably cine) DICOM instances are currently
--- a/Sphinx/source/faq/troubleshooting.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/troubleshooting.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -5,7 +5,7 @@
 
 As a general rule, when you encounter an issue, always make sure that
 you use the `most recent version
-<http://www.orthanc-server.com/download.php>`__ of Orthanc.
+<https://www.orthanc-server.com/download.php>`__ of Orthanc.
 
 Also make a search on the `Orthanc Users discussion group
 <https://groups.google.com/forum/#!forum/orthanc-users>`__, and make a
@@ -65,14 +65,14 @@
 
 * **Orthanc slows down if storing many files**: The default database
   engine that is built in Orthanc is `SQLite
-  <https://www.sqlite.org/>`__. As SQLite is above all a lightweight
-  database engine, it is not designed to `store very large datasets
-  <https://www.sqlite.org/whentouse.html>`__. If you are sure that you
-  have properly disabled run-time debug assertions (cf. above), but
-  still experience degradation in performance over time, you should
-  seriously consider switching to a more scalable database engine. To
-  this end, you can notably check out the :ref:`official PostgreSQL
-  plugin <postgresql>`.
+  <https://www.sqlite.org/index.html>`__. As SQLite is above all a
+  lightweight database engine, it is not designed to `store very large
+  datasets <https://www.sqlite.org/whentouse.html>`__. If you are sure
+  that you have properly disabled run-time debug assertions
+  (cf. above), but still experience degradation in performance over
+  time, you should seriously consider switching to a more scalable
+  database engine. To this end, you can notably check out the
+  :ref:`official PostgreSQL plugin <postgresql>`.
 
   As a rule of thumb, the performance of the default SQLite engine
   built in Orthanc should run fine up to about 50,000 DICOM instances.
@@ -94,9 +94,9 @@
 
   - As an alternative, you can disable IPv6 support. This is a
     Windows-specific problem that is discussed `here
-    <http://superuser.com/questions/43823/google-chrome-is-slow-to-localhost>`__
+    <https://superuser.com/questions/43823/google-chrome-is-slow-to-localhost>`__
     and `here
-    <http://stackoverflow.com/questions/1726585/firefox-and-chrome-slow-on-localhost-known-fix-doesnt-work-on-windows-7>`__.
+    <https://stackoverflow.com/questions/1726585/firefox-and-chrome-slow-on-localhost-known-fix-doesnt-work-on-windows-7>`__.
 
 * If you experience **slow DICOM transfers under GNU/Linux**, please
   read the `following bug report
@@ -136,9 +136,9 @@
 * If **Orthanc crashes when handling one large DICOM file**, this most
   probably indicates a memory allocation error. Indeed, the `official
   Windows binaries
-  <http://www.orthanc-server.com/download-windows.php>`__ are compiled
+  <https://www.orthanc-server.com/download-windows.php>`__ are compiled
   using a 32bit compiler. As a consequence, Orthanc only has access to
   less than 4GB of RAM. If this is an important limitation for you,
   precompiled command-line versions of Orthanc for Windows 64bit are
   available courtesy of `Osimis
-  <http://www.osimis.io/en/download.html>`__.
+  <https://www.osimis.io/en/download.html>`__.
--- a/Sphinx/source/faq/video.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/video.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -32,7 +32,7 @@
    Explorer <orthanc-explorer>` is able to display the individual
    frames and manually navigate between them through keyboard.
 2. The official `Web viewer plugin
-   <http://www.orthanc-server.com/static.php?page=web-viewer>`__ will
+   <https://www.orthanc-server.com/static.php?page=web-viewer>`__ will
    allow you to use the mouse scroll wheel to display the successive
    frames of the video.
 
--- a/Sphinx/source/faq/viewers.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/viewers.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -14,24 +14,24 @@
 <mailto:s.jodogne@orthanc-labs.com>`__ about other compatible FOSS):
 
 * `Open Health Imaging Foundation (OHIF) <https://docs.ohif.org/>`__.
-* `Horos <https://www.horosproject.org/>`__.
-* `Gingko CADx <https://www.ginkgo-cadx.com/>`__ (a
+* `Horos <https://horosproject.org/>`__.
+* `Gingko CADx <http://ginkgo-cadx.com/en/>`__ (a
   :ref:`configuration guide <ginkgo-cadx>` is available).
 * `3D Slicer <https://www.slicer.org/>`__.
 * `medInria <https://med.inria.fr/>`__.
 * `Aeskulap <https://github.com/pipelka/aeskulap>`__.
-* `OsiriX <http://www.osirix-viewer.com/>`__ (note however that the
+* `OsiriX <https://www.osirix-viewer.com/>`__ (note however that the
   openness of this particular software is `currently subject to
   discussion
-  <http://blog.purview.net/an-open-letter-to-the-osirix-community>`__).
+  <https://www.purview.net/blog/an-open-letter-to-the-osirix-community>`__).
 
 Make also sure to check out the following extensions to Orthanc:
 
-* `Orthanc Web viewer plugin <http://www.orthanc-server.com/static.php?page=web-viewer>`__.
+* `Orthanc Web viewer plugin <https://www.orthanc-server.com/static.php?page=web-viewer>`__.
 * `Osimis Web viewer plugin (Advanced version of the Orthanc Web viewer)
   <https://www.orthanc-server.com/static.php?page=osimis-web-viewer>`__.
-* `ImageJ extension <http://www.orthanc-server.com/static.php?page=imagej>`__.
-* `Stone of Orthanc <http://www.orthanc-server.com/static.php?page=stone>`__.
+* `ImageJ extension <https://www.orthanc-server.com/static.php?page=imagej>`__.
+* `Stone of Orthanc <https://www.orthanc-server.com/static.php?page=stone>`__.
 * `dwv-orthanc-plugin
   <https://github.com/ivmartel/dwv-orthanc-plugin>`__ by Yves
   Martelli, that embeds `dwv
--- a/Sphinx/source/faq/why-orthanc.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/why-orthanc.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -1,10 +1,9 @@
 Why "Orthanc"?
 ==============
 
-The spelling "`Orthanc
-<https://en.wikipedia.org/wiki/Orthanc#Orthanc>`__" originates from
-`J.R.R. Tolkien <https://en.wikipedia.org/wiki/J._R._R._Tolkien>`__'s
-work.
+The spelling "`Orthanc <https://en.wikipedia.org/wiki/Isengard>`__"
+originates from `J.R.R. Tolkien
+<https://en.wikipedia.org/wiki/J._R._R._Tolkien>`__'s work.
 
 Orthanc is the black tower of Isengard that houses one of the
 **palantíri**. A `palantír
--- a/Sphinx/source/faq/worklist.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/faq/worklist.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -24,10 +24,10 @@
 distribution of Orthanc to serve the worklists stored in some folder
 on the filesystem. This sample plugin mimics the behavior of the
 ``wlmscpfs`` command-line tool from the `DCMTK software
-<http://support.dcmtk.org/docs/wlmscpfs.html>`__.
+<https://support.dcmtk.org/docs/wlmscpfs.html>`__.
 
 For more complex or integrated workflows where you must implement a
 custom MWL plugin, please check the `documentation of the part of the
 Orthanc plugin SDK
-<http://sdk.orthanc-server.com/group__DicomCallbacks.html#ga23080c4e871b8428ede61d9841c10d76>`__
+<https://sdk.orthanc-server.com/group__DicomCallbacks.html#ga23080c4e871b8428ede61d9841c10d76>`__
 that is related to the management of worklists.
--- a/Sphinx/source/index.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/index.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -8,7 +8,7 @@
 
 This site documents Orthanc. If you want to access more general
 information about Orthanc, please go to the `official Web site
-<http://www.orthanc-server.com>`_.
+<https://www.orthanc-server.com>`_.
 
 
 Contents
--- a/Sphinx/source/plugins.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -70,7 +70,7 @@
 
 * `AWS S3 storage plugin
   <https://github.com/radpointhq/orthanc-s3-storage>`__: This plugin
-  by `Radpoint <https://www.radpoint.pl/>`__ makes Orthanc store its
+  by `Radpoint <https://radpoint.pl/>`__ makes Orthanc store its
   DICOM files into an `Amazon S3 bucket
   <https://en.wikipedia.org/wiki/Amazon_S3>`__.
 * `DWV Orthanc Plugin
@@ -80,7 +80,7 @@
   Web viewer of DICOM images.
 * Another Web viewer is provided courtesy of `Emsy Chan
   <https://groups.google.com/d/msg/orthanc-users/EC5Z2KaM4Hs/MG3KkzhCDAAJ>`__.
-* `VPI Reveal <http://www.vpireveal.com/>`__ provides a plugin to
+* `VPI Reveal <https://www.vpireveal.com/>`__ provides a plugin to
   "write the DICOM records in a normal Windows-readable file hierarchy
   (patient-study-series-DICOM file) at a location called
   ``VPIStorage`` that can then be imported into VPI Reveal."  `Check
@@ -97,5 +97,5 @@
   might contain plugins that are not tracked in this list.
 
 *Remark:* Do not hesitate to `contact us
-<http://www.orthanc-server.com/static.php?page=contact>`__ if you have
+<https://www.orthanc-server.com/static.php?page=contact>`__ if you have
 developed a plugin so that we can promote it in the list above!
--- a/Sphinx/source/plugins/dicomweb.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/dicomweb.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -15,7 +15,7 @@
 into a **DICOMweb client**.
 
 For general information, check out the `official homepage of the
-plugins <http://www.orthanc-server.com/static.php?page=dicomweb>`__.
+plugins <https://www.orthanc-server.com/static.php?page=dicomweb>`__.
 
 The full standard is not implemented yet, the supported features are
 `tracked in the repository
@@ -39,12 +39,12 @@
 The compilation will produce a shared library ``OrthancDicomWeb`` that
 contains the DICOMweb plugin. Pre-compiled binaries for Microsoft
 Windows `are also available
-<http://www.orthanc-server.com/browse.php?path=/plugin-dicom-web>`__,
+<https://www.orthanc-server.com/browse.php?path=/plugin-dicom-web>`__,
 and are included in the `Windows installers
 <https://www.orthanc-server.com/download-windows.php>`__.  A package
 for `Apple's Mac OS X
-<http://localhost/~jodogne/orthanc/static.php?page=download-mac>`__ is
-available courtesy of `Osimis <http://osimis.io/>`__.
+<https://www.orthanc-server.com/static.php?page=download-mac>`__ is
+available courtesy of `Osimis <https://www.osimis.io/>`__.
 
 *Remark:* Some older build instructions are also available in the
 `source distribution
@@ -388,8 +388,8 @@
 
 Here is a direct link to the DICOMweb client running on our demo
 server:
-`http://demo.orthanc-server.com/dicom-web/app/client/index.html
-<http://demo.orthanc-server.com/dicom-web/app/client/index.html>`__
+`https://demo.orthanc-server.com/dicom-web/app/client/index.html
+<https://demo.orthanc-server.com/dicom-web/app/client/index.html>`__
 
 
 
@@ -399,7 +399,8 @@
 Once your Orthanc server is properly configured (see above), you can
 make REST calls to the API of the DICOMweb server. For demonstration
 purpose, this section makes the assumption that the ``VIX`` dataset
-provided by `OsiriX <http://www.osirix-viewer.com/datasets/>`__ has
+provided by `OsiriX
+<https://www.osirix-viewer.com/resources/dicom-image-library/>`__ has
 been uploaded to Orthanc.
 
 WADO-URI
@@ -536,7 +537,8 @@
 <https://en.wikipedia.org/wiki/Percent-encoding>`__.
 
 An user-friendly reference of the features available in QIDO-RS and
-WADO-RS `can be found on this site <http://www.dicomweb.org/>`__.
+WADO-RS `can be found on this site
+<https://www.dicomstandard.org/dicomweb/>`__.
 
 
 Sending DICOM resources to a STOW-RS server
--- a/Sphinx/source/plugins/google-cloud-platform.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/google-cloud-platform.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -58,7 +58,7 @@
 The compilation produces a shared library
 ``OrthancGoogleCloudPlatform`` that contains the GCP
 plugin. Pre-compiled binaries for Microsoft Windows `are available
-<http://www.orthanc-server.com/browse.php?path=/plugin-google-cloud>`__,
+<https://www.orthanc-server.com/browse.php?path=/plugin-google-cloud>`__,
 and are included in the `Windows installers
 <https://www.orthanc-server.com/download-windows.php>`__.
 
@@ -125,14 +125,14 @@
 ^^^^^^^^^^^^^^^
 
 As explained on the `Google documentation
-<https://cloud.google.com/docs/authentication/#service_accounts>`__,
-*"a service account is a Google account that represents an
-application, as opposed to representing an end user"*. This is
-presumably the most common situation in the case of Orthanc.
+<https://cloud.google.com/docs/authentication>`__, *"a service account
+is a Google account that represents an application, as opposed to
+representing an end user"*. This is presumably the most common
+situation in the case of Orthanc.
 
 You first have to `create a service account
-<https://cloud.google.com/docs/authentication/getting-started#creating_a_service_account>`__
-for your application. This will produce a JSON file (say,
+<https://cloud.google.com/docs/authentication/getting-started>`__ for
+your application. This will produce a JSON file (say,
 ``dicom-osimis.json``) that you have to store securely on the server
 that will run Orthanc.
 
@@ -173,7 +173,7 @@
 User account is an alternative to service account, and can be used
 *"when the application needs to access resources on behalf of an end
 user"* (check out the `Google documentation
-<https://cloud.google.com/docs/authentication/#user_accounts>`__).
+<https://cloud.google.com/docs/authentication/end-user>`__).
 
 .. highlight:: json
 
--- a/Sphinx/source/plugins/mysql.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/mysql.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -11,7 +11,7 @@
 by a MySQL or a MariaDB database.
 
 For general information, check out the `official homepage of the
-plugins <http://www.orthanc-server.com/static.php?page=mysql>`__.
+plugins <https://www.orthanc-server.com/static.php?page=mysql>`__.
 
 **Warning:** According to `this thread on our discussion group
 <https://groups.google.com/d/msg/orthanc-users/yV3LSTh_TjI/Fb4ShaYMBAAJ>`__,
@@ -47,7 +47,7 @@
 ^^^^^^^^^^^^^^^^^
 
 Pre-compiled binaries for Microsoft Windows `are also available
-<http://www.orthanc-server.com/browse.php?path=/plugin-mysql>`__.
+<https://www.orthanc-server.com/browse.php?path=/plugin-mysql>`__.
 
 
 Dynamic linking on Ubuntu 16.04
@@ -161,7 +161,7 @@
 
 By default, the plugins lock the database (using `MySQL/MariaDB
 "GET_LOCK()"
-<https://dev.mysql.com/doc/refman/8.0/en/miscellaneous-functions.html#function_get-lock>`__)
+<https://dev.mysql.com/doc/refman/8.0/en/locking-functions.html>`__)
 to prevent other instances of Orthanc from using the same database. If
 you want several instances of Orthanc to share the same database, set
 the ``Lock`` option to ``false`` in the configuration file.
--- a/Sphinx/source/plugins/osimis-webviewer.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/osimis-webviewer.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -13,7 +13,7 @@
 
 For general information, check out the `official homepage of the
 plugin
-<http://www.orthanc-server.com/static.php?page=osimis-web-viewer>`__.
+<https://www.orthanc-server.com/static.php?page=osimis-web-viewer>`__.
 Also `check out the source code
 <https://bitbucket.org/osimis/osimis-webviewer-plugin>`__.
 
@@ -107,7 +107,7 @@
   of the sets of codecs supported by the `DICOM standard
   <http://dicom.nema.org/medical/dicom/current/output/chtml/part05/PS3.5.html>`__
   and those supported by the `web browsers
-  <https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats>`__.
+  <https://developer.mozilla.org/en-US/docs/Web/Media/Formats>`__.
   In short, this mostly comes down to just MPEG-4.
   
 - **Where are the annotations stored ?**
--- a/Sphinx/source/plugins/postgresql.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/postgresql.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -11,7 +11,7 @@
 by a PostgreSQL database.
 
 For general information, check out the `official homepage of the
-plugins <http://www.orthanc-server.com/static.php?page=postgresql>`__.
+plugins <https://www.orthanc-server.com/static.php?page=postgresql>`__.
 
 
 
@@ -42,10 +42,10 @@
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Pre-compiled binaries for Microsoft Windows `are also available
-<http://www.orthanc-server.com/browse.php?path=/plugin-postgresql>`__.
+<https://www.orthanc-server.com/browse.php?path=/plugin-postgresql>`__.
 A package for `Apple's Mac OS X
-<http://www.osimis.io/en/download.html>`__
-is available courtesy of `Osimis <http://osimis.io/>`__.
+<https://www.osimis.io/en/download.html>`__
+is available courtesy of `Osimis <https://www.osimis.io/>`__.
 
 
 .. _postgresql-ubuntu1604:
@@ -100,7 +100,7 @@
 version above 0.9.5. You then have to **create a database** dedicated
 to Orthanc on some PostgreSQL server. Please refer to the `PostgreSQL
 documentation
-<https://www.postgresql.org/docs/current/static/tutorial-createdb.html>`__.
+<https://www.postgresql.org/docs/current/tutorial-createdb.html>`__.
 
 Once Orthanc is installed and the database is created, you must add a
 section in the :ref:`configuration file <configuration>` that
@@ -180,7 +180,7 @@
 
 Instead of specifying explicit authentication parameters, you can also
 use the `PostgreSQL connection URIs syntax
-<https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING>`__. For
+<https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING>`__. For
 instance::
 
   {
@@ -199,7 +199,7 @@
 
 **Remark:** The Debian Med project maintains `another useful set of
 instructions
-<https://anonscm.debian.org/viewvc/debian-med/trunk/packages/orthanc-postgresql/trunk/debian/README.Debian?view=markup>`__.
+<https://salsa.debian.org/med-team/orthanc-postgresql/-/blob/master/debian/README.Debian>`__.
 
 
 Advanced options
@@ -218,7 +218,7 @@
 
 By default, the plugins lock the database (using `PostgreSQL advisory
 locks
-<https://www.postgresql.org/docs/current/static/functions-admin.html#FUNCTIONS-ADVISORY-LOCKS>`__)
+<https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-ADVISORY-LOCKS>`__)
 to prevent other instances of Orthanc from using the same PostgreSQL
 database. If you want several instances of Orthanc to share the same
 database, set the ``Lock`` option to ``false`` in the configuration
@@ -280,5 +280,5 @@
 
 This is due to a timeout in the PostgreSQL server. Please make sure to
 `enable keep-alive
-<http://dba.stackexchange.com/questions/97534/is-there-a-timeout-option-for-remote-access-to-postgresql-database>`__
+<https://dba.stackexchange.com/questions/97534/is-there-a-timeout-option-for-remote-access-to-postgresql-database>`__
 in the configuration of your PostgreSQL server
--- a/Sphinx/source/plugins/transfers.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/transfers.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -84,7 +84,7 @@
 ^^^^^^^^^^^^^^^^^
 
 Pre-compiled binaries for Microsoft Windows `are available
-<http://www.orthanc-server.com/browse.php?path=/plugin-transfers>`__.
+<https://www.orthanc-server.com/browse.php?path=/plugin-transfers>`__.
 
 
 Dynamic linking on Ubuntu 16.04
--- a/Sphinx/source/plugins/webviewer.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/webviewer.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -9,7 +9,7 @@
 This **official** plugin extends Orthanc with a Web viewer of medical images.
 
 For general information, check out the `official homepage of the
-plugin <http://www.orthanc-server.com/static.php?page=web-viewer>`__.
+plugin <https://www.orthanc-server.com/static.php?page=web-viewer>`__.
 
 
 Compilation
@@ -29,7 +29,7 @@
 The compilation will produce a shared library ``OrthancWebViewer``
 that contains the Web viewer plugin.  Pre-compiled binaries for
 Microsoft Windows `are also available
-<http://www.orthanc-server.com/browse.php?path=/plugin-webviewer>`__.
+<https://www.orthanc-server.com/browse.php?path=/plugin-webviewer>`__.
 
 *Remark:* Some older build instructions are also available in the
 `source distribution
@@ -77,7 +77,7 @@
 Explorer, a yellow button entitled ``Orthanc Web Viewer`` will show
 up. It will open the Web viewer for that particular series.  See also
 the demonstration video on `official homepage of the plugin
-<http://www.orthanc-server.com/static.php?page=web-viewer>`__.
+<https://www.orthanc-server.com/static.php?page=web-viewer>`__.
 
 
 Advanced options
@@ -111,7 +111,7 @@
 * ``EnableGdcm`` specifies whether `GDCM
   <https://sourceforge.net/projects/gdcm/>`__ should be used to decode
   DICOM images, replacing the built-in decoder of Orthanc that
-  internally uses `DCMTK <http://dicom.offis.de/dcmtk.php.en>`__.
+  internally uses `DCMTK <https://dicom.offis.de/dcmtk.php.en>`__.
   This is notably necessary to deal with DICOM images encoded using
   `JPEG2000 <https://en.wikipedia.org/wiki/JPEG_2000>`__, as this
   format is not readily supported by the core version of DCMTK.  By
--- a/Sphinx/source/plugins/worklists-plugin.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/worklists-plugin.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -12,12 +12,12 @@
 The sample plugin will serve the worklists stored in some folder on
 the filesystem. This mimics the behavior of the ``wlmscpfs``
 command-line tool from the `DCMTK software
-<http://support.dcmtk.org/docs/wlmscpfs.html>`__. 
+<https://support.dcmtk.org/docs/wlmscpfs.html>`__. 
 
 The worklists to be served must be put inside the folder of interest
 by an external application or script (note: files must have a ``.wl`` extension). ``dump2dcm`` might be a very
 `useful companion tool
-<http://support.dcmtk.org/docs/dump2dcm.html>`__ to generate such
+<https://support.dcmtk.org/docs/dump2dcm.html>`__ to generate such
 worklist files. Whenever a C-Find SCP request is issued to Orthanc,
 the plugin will read the content of the folder of interest to locate
 the worklists that match the request. As a consequence, the external
@@ -62,7 +62,7 @@
 <https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/>`__
 contains a database of sample worklists, that comes from the DCMTK
 source distribution, as described in the `FAQ entry #37 of the DCMTK
-project <http://forum.dcmtk.org/viewtopic.php?t=84>`__.
+project <https://forum.dcmtk.org/viewtopic.php?t=84>`__.
 
 
 Tutorial
@@ -71,7 +71,7 @@
 .. highlight:: javascript
  
 - Download `DCMTK utilities
-  <http://dicom.offis.de/download/dcmtk/release/bin/>`__.
+  <https://dicom.offis.de/download/dcmtk/release/bin/>`__.
 - Download sample `worklist files
   <https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/>`__
   from the Orthanc source code and copy them in a dedicated folder.
@@ -93,7 +93,7 @@
 
 - The tests below will be done using the ``findscu`` command-line tool
   from the `DCMTK utilities
-  <http://support.dcmtk.org/docs/findscu.html>`__. Assuming
+  <https://support.dcmtk.org/docs/findscu.html>`__. Assuming
   ``findscu`` and Orthanc runs on the same computer (i.e. on the
   ``127.0.0.1`` localhost), declare the ``FINDSCU`` AET to the list of
   know modalities::
@@ -184,7 +184,7 @@
 
 When trying to retrieve worklists from a modality, one usually don't get debugging capabilities from the modality itself.
 Therefore, it is usually convenient to mimic the modality with ``findscu`` (provided by `DCMTK software
-<http://support.dcmtk.org/docs/wlmscpfs.html>`__).  
+<https://support.dcmtk.org/docs/wlmscpfs.html>`__).  
 
 - First, you should make sure that you have configured the Worklist plugin correctly and that you have pushed
   at least a ``.wl`` file in the worklist database.  For this, you should issue this kind of command::
--- a/Sphinx/source/plugins/wsi.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/plugins/wsi.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -18,7 +18,7 @@
    inside Orthanc, to a standard hierarchical TIFF image.
 
 For general information, check out the `official homepage of the
-framework <http://www.orthanc-server.com/static.php?page=wsi>`__. 
+framework <https://www.orthanc-server.com/static.php?page=wsi>`__. 
 
 
 Compilation
@@ -55,7 +55,7 @@
 ^^^^^^^^^^^^^^^^^
   
 Note that pre-compiled binaries for Microsoft Windows `are available
-<http://www.orthanc-server.com/browse.php?path=/whole-slide-imaging>`__.
+<https://www.orthanc-server.com/browse.php?path=/whole-slide-imaging>`__.
 
 
 Dynamic linking
@@ -113,7 +113,7 @@
 images. This button will open the WSI viewer for that particular
 series. This behavior can be seen on the Orthanc Explorer interface
 running on our `WSI demonstration server
-<http://wsi.orthanc-server.com/orthanc/app/explorer.html>`__.
+<https://wsi.orthanc-server.com/orthanc/app/explorer.html>`__.
 
 
 
@@ -221,7 +221,7 @@
 images. Some commonplace image formats (PNG and JPEG) can be
 DICOM-ized as well. However, whole-slide images can come in many
 proprietary file formats. To re-encode such images, the DICOM-izer
-relies upon the `OpenSlide toolbox <http://openslide.org/>`__.
+relies upon the `OpenSlide toolbox <https://openslide.org/>`__.
 
 For this feature to work, you have to tell the command-line tool where
 it can find the OpenSlide shared library. GNU/Linux distributions
@@ -232,7 +232,7 @@
   $ ./OrthancWSIDicomizer --openslide=libopenslide.so CMU-1-JP2K-33005.svs
 
 Pre-compiled Microsoft Windows binaries of this shared library can be
-found on the `OpenSlide homepage <http://openslide.org/download/>`__ (Note that
+found on the `OpenSlide homepage <https://openslide.org/download/>`__ (Note that
 you should copy all .dll files from the OpenSlide package next to the OrthancWSIDicomizer
 executable)::
 
--- a/Sphinx/source/users/backup.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/backup.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -34,7 +34,7 @@
 for the official Debian package of Orthanc that automates this backup
 procedure. Note that in this script, the call to the SQLite
 command-line tool is used to force the `WAL replay
-<http://www.sqlite.org/wal.html>`__. This manual replay should not be
+<https://www.sqlite.org/wal.html>`__. This manual replay should not be
 necessary for Orthanc >= 0.7.3.
 
 
@@ -44,15 +44,15 @@
 The default SQLite engine is well adapted for DICOM routing or for
 image buffering tasks, but not for enterprise scenarios. In such
 cases, you are highly recommended to use the `PostgreSQL back-end
-<http://www.orthanc-server.com/static.php?page=postgresql>`__ or the
+<https://www.orthanc-server.com/static.php?page=postgresql>`__ or the
 `MySQL/MariaDB back-end
-<http://www.orthanc-server.com/static.php?page=mysql>`__.
+<https://www.orthanc-server.com/static.php?page=mysql>`__.
 
 If using PostgreSQL, you can do hot backups (i.e. while Orthanc is
 running), and you benefit from all the flexibility of PostgreSQL
 backup. These procedures are out of the scope of this manual.  Please
 check the `official backup and restore manual
-<https://www.postgresql.org/docs/devel/static/backup.html>`__.
+<https://www.postgresql.org/docs/devel/backup.html>`__.
 
 Similar backup procedures are available for MySQL and MariaDB as
 well. Please check the official manual about `database backup methods
--- a/Sphinx/source/users/cookbook.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/cookbook.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -15,11 +15,11 @@
 
 To obtain the Orthanc binaries, you have several possibilities:
 
-* `Download pre-compiled packages <http://www.orthanc-server.com/download.php>`__.
+* `Download pre-compiled packages <https://www.orthanc-server.com/download.php>`__.
 * :ref:`Use Docker <docker>`.
 * :ref:`Compile Orthanc by yourself <compiling>`.
 * External contributors are also maintaining `Vagrant VM for Orthanc
-  <https://github.com/jodogne/OrthancContributed/blob/master/Links.md#vagrant>`__.
+  <https://github.com/jodogne/OrthancContributed/blob/master/Links.md#user-content-vagrant>`__.
 
 
 .. _orthanc-explorer:
@@ -66,8 +66,8 @@
 connect your modality to Orthanc.
 
 You can also use the standard command-line tool ``storescu`` from the
-`DCMTK software <http://dicom.offis.de/dcmtk.php.en>`__ to 
-manually send DICOM images to Orthanc, for instance::
+`DCMTK software <https://dicom.offis.de/dcmtk.php.en>`__ to manually
+send DICOM images to Orthanc, for instance::
 
     $ storescu -aec ORTHANC localhost 4242 *.dcm
 
--- a/Sphinx/source/users/docker.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/docker.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -26,8 +26,8 @@
   configuration system that is inherited from the Debian packages
   (i.e. manual edition of the configuration files).
 
-* Our commercial partner `Osimis <http://osimis.io>`__ also `publishes
-  separated Docker images
+* Our commercial partner `Osimis <https://www.osimis.io>`__ also
+  `publishes separated Docker images
   <https://osimis.atlassian.net/wiki/spaces/OKB/pages/26738689/How+to+use+osimis+orthanc+Docker+images>`__.
   These ``osimis/orthanc`` images are used by the technical team of
   Osimis in order to provide professional support to their customers,
@@ -156,8 +156,8 @@
 expected format).
 
 If you have a source image that is not a hierarchical TIFF, you must
-instruct the Dicomizer to use `OpenSlide <http://openslide.org/>`__ to
-decode it by adding the ``--openslide`` option::
+instruct the Dicomizer to use `OpenSlide <https://openslide.org/>`__
+to decode it by adding the ``--openslide`` option::
 
   $ sudo docker run -t -i --rm --link=orthanc-wsi:orthanc --entrypoint=OrthancWSIDicomizer -v /tmp/Source.svs:/tmp/Source.svs:ro jodogne/orthanc-plugins --username=orthanc --password=orthanc --orthanc=http://orthanc:8042/ --openslide=libopenslide.so /tmp/Source.svs
 
--- a/Sphinx/source/users/lua.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/lua.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -46,8 +46,8 @@
 *Note:* The ``--data-binary`` cURL option is used instead of
 ``--data`` to prevent the interpretation of newlines by cURL, which is
 `mandatory for the proper evaluation
-<http://stackoverflow.com/questions/3872427/how-to-send-line-break-with-curl>`__ of the possible
-comments inside the Lua script.
+<https://stackoverflow.com/questions/3872427/how-to-send-line-break-with-curl>`__
+of the possible comments inside the Lua script.
 
 Lua API
 -------
--- a/Sphinx/source/users/replication.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/replication.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -86,9 +86,9 @@
 * The source Orthanc uses the default storage area on the filesystem
   (i.e. the source Orthanc does *not* store its DICOM files using one
   of the "storage area plugins", such as for `PostgreSQL
-  <http://www.orthanc-server.com/static.php?page=postgresql>`_ or
+  <https://www.orthanc-server.com/static.php?page=postgresql>`_ or
   `MySQL/MariaDB
-  <http://www.orthanc-server.com/static.php?page=mysql>`_ - but it's
+  <https://www.orthanc-server.com/static.php?page=mysql>`_ - but it's
   OK for the source of Orthanc to use any of the "index plugins"),
 * You have command-line access to the source Orthanc, and
 * The transparent :ref:`compression` of the DICOM instances is
--- a/Sphinx/source/users/rest.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/rest.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -52,7 +52,7 @@
 
 Note that in the case of curl, setting the ``Expect`` HTTP Header will
 significantly `reduce the execution time of POST requests
-<http://stackoverflow.com/questions/463144/php-http-post-fails-when-curl-data-1024/463277#463277>`__::
+<https://stackoverflow.com/questions/463144/php-http-post-fails-when-curl-data-1024/463277#463277>`__::
 
     $ curl -X POST -H "Expect:" http://localhost:8042/instances --data-binary @CT.X.1.2.276.0.7230010.dcm
 
@@ -1011,7 +1011,7 @@
 * The full documentation of the REST API is maintained as an online
   spreadsheet accessible from the `documentation part of the official
   Web site
-  <http://www.orthanc-server.com/static.php?page=documentation>`__
+  <https://www.orthanc-server.com/static.php?page=documentation>`__
   (click on the *Reference of the REST API* button).
 * A documentation of the REST API in the OpenAPI/Swagger format is
   `available as work-in-progress <https://api.orthanc-server.com/>`__.
--- a/Sphinx/source/users/storage-commitment.rst	Mon Mar 30 07:59:50 2020 +0200
+++ b/Sphinx/source/users/storage-commitment.rst	Mon Mar 30 18:47:35 2020 +0200
@@ -183,7 +183,7 @@
 
 The custom storage commitment SCP is installed in the Orthanc core by
 using the ``OrthancPluginRegisterStorageCommitmentScpCallback()``
-function of the `plugin SDK <http://sdk.orthanc-server.com/>`__.
+function of the `plugin SDK <https://sdk.orthanc-server.com/>`__.
 
 Importantly, this primitive frees the plugin developer from manually
 creating the Orthanc jobs. One job is transparently created by the