links: Replace tons of http with https

ElektraInitiative · Jan 11, 2023 · ce8c633 · ce8c633
1 parent e6c6ec4
commit ce8c633
Show file tree

Hide file tree

Showing 27 changed files with 63 additions and 63 deletions.
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -68,7 +68,7 @@ members.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+available at [https://contributor-covenant.org/version/1/4][version]
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/
diff --git a/doc/AUTHORS.md b/doc/AUTHORS.md
@@ -108,7 +108,7 @@ improvements to the dbus plugin
 development of the crypto plugin, minor bug fixes, BSD/macOS support
 
 - email: [email protected]
-- GitHub user: [petermax2](http://github.com/petermax2)
+- GitHub user: [petermax2](https://github.com/petermax2)
 - devel on: Fedora
 - test on: Fedora, Debian, macOS
 
@@ -117,7 +117,7 @@ development of the crypto plugin, minor bug fixes, BSD/macOS support
 documentation, bug fixes
 
 - email: [email protected]
-- GitHub user: [sanssecours](http://github.com/sanssecours)
+- GitHub user: [sanssecours](https://github.com/sanssecours)
 - devel/test on: macOS
 
 ## Marvin Mall

diff --git a/doc/CODING.md b/doc/CODING.md
@@ -20,7 +20,7 @@ You can find more information about the structure in the `README.md`.
 - Make sure that the codestyle of contributions complies with the already established codestyle of this project, except if this document
   says otherwise: then please open an issue for offending code.
 - We use Unix line endings
-- Large files should be in http://blobs.libelektra.org/ or https://rawdata.libelektra.org
+- Large files should be in https://blobs.libelektra.org/ or https://rawdata.libelektra.org
 - `find . -not -regex '[/.a-zA-Z0-9_-]*'` should not find your file names
 
 ## Source Code
@@ -158,7 +158,7 @@ On macOS you can install `clang-format` using [Homebrew][] either directly:
 brew install clang-format
 ```
 
-or by installing the whole [LLVM](http://llvm.org) infrastructure:
+or by installing the whole [LLVM](https://llvm.org) infrastructure:
 
 ```sh
 brew install llvm

diff --git a/doc/COMPILE.md b/doc/COMPILE.md
@@ -19,7 +19,7 @@ clang are also supported but not described here). Those can be installed as foll
   sudo yum install -y cmake git gcc-c++ make
   ```
 
-- on macOS, most of the build tools can be obtained by installing Xcode (from the App Store). Other required tools may be installed using [brew](http://brew.sh/). First install brew as described on their website. Then issue the following command to get CMake and Git in order to complete the basic requirements:
+- on macOS, most of the build tools can be obtained by installing Xcode (from the App Store). Other required tools may be installed using [brew](https://brew.sh/). First install brew as described on their website. Then issue the following command to get cmake and git in order to complete the basic requirements:
 
   ```sh
   brew install cmake git
@@ -425,7 +425,7 @@ For a list of available bindings see
 
 `Debug`, `Release` or `RelWithDebInfo`
 See help bar at bottom of `ccmake` for that option or:
-http://www.cmake.org/Wiki/CMake_Useful_Variables
+https://www.cmake.org/Wiki/CMake_Useful_Variables
 
 #### `BUILD_SHARED`, `BUILD_FULL` and `BUILD_STATIC`
 
@@ -686,7 +686,7 @@ Please enable EPEL https://fedoraproject.org/wiki/EPEL
 ```sh
 # Install EPEL for RHEL 7
 curl -o epel-release-7-8.noarch.rpm \
-  http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.noarch.rpm
+  https://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.noarch.rpm
 sudo rpm -ivh epel-release-7-8.noarch.rpm
 sudo yum update
 ```

diff --git a/doc/INSTALL.md b/doc/INSTALL.md
@@ -181,13 +181,13 @@ make package # See CPack below
 
 ## macOS
 
-You can install Elektra using [Homebrew](http://brew.sh) via the shell command:
+You can install Elektra using [Homebrew](https://brew.sh) via the shell command:
 
 ```sh
 brew install elektra
 ```
 
-. We also provide a tap containing a more elaborate formula [here](http://github.com/ElektraInitiative/homebrew-elektra).
+. We also provide a tap containing a more elaborate formula [here](https://github.com/ElektraInitiative/homebrew-elektra).
 
 ## Windows
 

diff --git a/doc/README.md b/doc/README.md
@@ -11,7 +11,7 @@ This folder contains documentation for “Elektra – the configuration framewor
 - [Security](SECURITY.md): This guideline shows how Elektra handles security concerns.
 - [Tutorials](tutorials): The tutorials folder provides various **user related tutorials**. If you are interested in **developer related tutorials** instead, then please take a look at the folder [dev](dev).
 - [News](news): The news folder contains release notes and other recent information about Elektra.
-- [Paper](paper): This directory contains a research paper about Elektra, also available in [PDF](http://joss.theoj.org/papers/10.21105/joss.00044) format.
+- [Paper](paper): This directory contains a research paper about Elektra, also available in [PDF](https://joss.theoj.org/papers/10.21105/joss.00044) format.
 
 ## Using Elektra
 
@@ -39,7 +39,7 @@ This folder contains documentation for “Elektra – the configuration framewor
 
 - [Coding](CODING.md): The coding guidelines describe the basic rules you should keep in mind when you want to contribute code to Elektra.
 - [Git](Git.md): This document describes how we use the version control system [Git](https://git-scm.com) to develop Elektra.
-- [Ideas](IDEAS.md): If you want to contribute to Elektra and do not know what, you can either take a look here or at our [issue tracker](http://libelektra.org/issues).
+- [Ideas](IDEAS.md): If you want to contribute to Elektra and do not know what, you can either take a look here or at our [issue tracker](https://libelektra.org/issues).
 - [ToDo](todo): This folder contains various ToDo items for future releases of Elektra.
 - [Authors](AUTHORS.md): This file lists information about Elektra’s authors.
 

diff --git a/doc/SECURITY.md b/doc/SECURITY.md
@@ -37,7 +37,7 @@ be a security risk.
 Can be changed using standard CMake ways.
 Some hints:
 
-http://wiki.debian.org/Hardening
+https://wiki.debian.org/Hardening
 
 ## Memory Leaks
 

diff --git a/doc/TESTING.md b/doc/TESTING.md
@@ -389,7 +389,7 @@ following section show how the most common ones can be used with `libelektra`.
 
 #### Cppcheck
 
-[Cppcheck](http://cppcheck.sourceforge.net/) can be used directly on a C or C++ source
+[Cppcheck](https://cppcheck.sourceforge.net/) can be used directly on a C or C++ source
 file by calling it with `cppcheck --enable=all <sourcefile>`. This way it might miss some header
 files though and thus doesn't detect all possible issues, but still gives useful hints in general.
 
@@ -413,7 +413,7 @@ of the issues found in the whole project.
 
 #### OCLint
 
-[OCLint](http://oclint.org/) is a static code analyzer for C, C++ and Objective C. To use this tool enable the CMake option `CMAKE_EXPORT_COMPILE_COMMANDS`. The steps below show a step-by-step guide on how to analyze files with OCLint.
+[OCLint](https://oclint.org/) is a static code analyzer for C, C++ and Objective C. To use this tool enable the CMake option `CMAKE_EXPORT_COMPILE_COMMANDS`. The steps below show a step-by-step guide on how to analyze files with OCLint.
 
 1. Create a build directory if you have not done so already and change the working path to this directory:
 
@@ -443,7 +443,7 @@ of the issues found in the whole project.
 
 #### scan-build
 
-[scan-build](http://clang-analyzer.llvm.org/scan-build.html) is a tool that is usually bundled along
+[scan-build](https://clang-analyzer.llvm.org/scan-build.html) is a tool that is usually bundled along
 with LLVM/Clang and is also primarily intended for C and C++ code. On macOS you have to install the
 package `llvm` with homebrew, then you'll find the tool in the folder `/usr/local/opt/llvm/bin/`.
 
@@ -472,7 +472,7 @@ the report is enriched with further information.
 
 #### SonarLint
 
-[SonarLint](http://www.sonarlint.org/) is a static code checker primarily intended for Java. It is
+[SonarLint](https://www.sonarlint.org/) is a static code checker primarily intended for Java. It is
 usually used by installing the corresponding plugin for the used IDE, then there is no further
 configuration required.
 

diff --git a/doc/VERSION.md b/doc/VERSION.md
@@ -123,8 +123,8 @@ For example, in `1.0` there is a deprecated method `ksNext` (not
 available in `kdb.h`). Thus in `2.0` it is subject to be removed.
 
 References:
-http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html
-http://packages.debian.org/de/sid/icheck
+https://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html
+https://packages.debian.org/de/sid/icheck
 
 ## Bindings
 

diff --git a/doc/WHO.md b/doc/WHO.md
@@ -11,7 +11,7 @@ configuration values can be shared (integrated).
 Known users:
 
 - [Oyranos](https://oyranos.org)
-- [LCDproc](http://lcdproc.omnipotent.net/) (in progress)
+- [LCDproc](https://lcdproc.omnipotent.net/) (in progress)
 - [KDE](https://kde.org) (in progress)
 - [OpenHAB](https://www.openhab.org/) (in progress)
 

diff --git a/doc/decisions/0b_rejected/elektra_web_pubsub.md b/doc/decisions/0b_rejected/elektra_web_pubsub.md
@@ -16,10 +16,10 @@ The idea is to use a Pub/Sub concept to synchronize actions which describe chang
 
 ## Considered Alternatives
 
-- [ZeroMQ](http://zeromq.org/): small and popular library for pub/sub
-- [nanomsg](http://nanomsg.org/): from the same author as ZeroMQ, even smaller - http://nanomsg.org/documentation-zeromq.html
+- [ZeroMQ](https://zeromq.org/): small and popular library for pub/sub
+- [nanomsg](https://nanomsg.org/): from the same author as ZeroMQ, even smaller - https://nanomsg.org/documentation-zeromq.html
 - [redis](https://redis.io/docs/manual/pubsub/): requires a running redis server
-- [kafka](http://kafka.apache.org/): seems too big for Elektra
+- [kafka](https://kafka.apache.org/): seems too big for Elektra
 - ZeroMQ with [JSMQ](https://github.com/zeromq/JSMQ).
 
 ## Decision

diff --git a/doc/decisions/3_decided/library_split.md b/doc/decisions/3_decided/library_split.md
@@ -7,7 +7,7 @@ Only `libelektra-core` is supposed to access private data, but this contradicts
 
 ## Constraints
 
-- The [C99 standard, section 5.2.4.1](http://www.open-std.org/jtc1/sc22/wg14/) gives following limit:
+- The [C99 standard, section 5.2.4.1](https://www.open-std.org/jtc1/sc22/wg14/) gives following limit:
   4095 external identifiers in one translation unit
 - Some parts of Elektra, like `mmapstorage` need access to private data structure.
 - Elektra does not support several different struct definitions of Key/KeySet.

diff --git a/doc/decisions/5_implemented/error_codes.md b/doc/decisions/5_implemented/error_codes.md
@@ -63,9 +63,9 @@ Various projects and standards:
   The registry does not use any specific error concept but takes the standard [Win32 Error Codes](https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d). These are neither hierarchical nor have any special ordering. Basically it is the same as Elektra has now except for no duplicated
   errors.
 - macOS X plist:
-  Just like Windows, plist uses standard macOS X errors which is a [huge catalog](http://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/) of unordered
+  Just like Windows, plist uses standard macOS X errors which is a [huge catalog](https://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/) of unordered
   return codes as integers.
-- [SNMP Standard](http://www.snmp.com/protocol/):
+- [SNMP Standard](https://www.snmp.com/protocol/):
   Being a standard network protocol, error codes are very specific to the domain itself. A list can be found [here](https://docs.microsoft.com/en-us/windows/desktop/snmp/snmp-error-codes) and would not meet the needs of Elektra at all.
 - POSIX:
   Returning a non-zero value and retrieving the concrete information from `errno` would not suffice for Elektra as it is too simple. It would not solve any of our current

diff --git a/doc/decisions/5_implemented/rest_api_documentation.md b/doc/decisions/5_implemented/rest_api_documentation.md
@@ -23,9 +23,9 @@ A standard way of describing REST APIs offered by tools and plugins for Elektra
 
 ## Considered Alternatives
 
-- [Swagger](http://swagger.io/)
+- [Swagger](https://swagger.io/)
 - [apiary](https://apiary.io/) with [API blueprints](https://apiblueprint.org/)
-- [RAML](http://raml.org/)
+- [RAML](https://raml.org/)
 
 ## Decision
 

diff --git a/doc/todo/OPTIMIZE b/doc/todo/OPTIMIZE
@@ -97,5 +97,5 @@ many globbing statements
 == DATA STRUCTURES ==
 
 improve memory footprint C structures:
-	http://www.catb.org/esr/structure-packing/?src=yc
+	https://www.catb.org/esr/structure-packing/?src=yc
 
diff --git a/doc/tutorials/highlevel-bindings.md b/doc/tutorials/highlevel-bindings.md
@@ -60,7 +60,7 @@ Your programming language of choice must provide a way to call into C code (like
 
 In general we prefer (in this order):
 
-1. Automatically and statically generated bindings (like [swig](http://www.swig.org/)).
+1. Automatically and statically generated bindings (like [swig](https://www.swig.org/)).
 2. Manually written bindings that directly call to library without any statically build part (like JNI and GI). They are a bit slower but can directly access libelektra.so.
 3. Manually written bindings that are built statically.
 

diff --git a/doc/tutorials/profiling.md b/doc/tutorials/profiling.md
@@ -205,7 +205,7 @@ llvm-xray account "$LOGFILE" -top=10 -sort=sum -sortorder=dsc -instr_map "$BUILD
 #> …
 ```
 
-. We can also use the log file to create a [Flame Graph](http://www.brendangregg.com/flamegraphs.html). To do that we use the `llvm-xray stack` to create an input file for the tool [`flamegraph.pl`][flamegraph]
+. We can also use the log file to create a [Flame Graph](https://www.brendangregg.com/flamegraphs.html). To do that we use the `llvm-xray stack` to create an input file for the tool [`flamegraph.pl`][flamegraph]
 
 ```sh
 llvm-xray stack "$LOGFILE" -stack-format=flame -aggregation-type=time -all-stacks \

diff --git a/doc/tutorials/python-kdb.md b/doc/tutorials/python-kdb.md
@@ -25,16 +25,16 @@ The [python bindings package](https://pkgs.alpinelinux.org/packages?name=py3-ele
 
 ```sh
 docker run -it alpine:edge /bin/sh
-echo "http://dl-cdn.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories
+echo "https://dl-cdn.alpinelinux.org/alpine/edge/testing" >> /etc/apk/repositories
 # Install elektra and the python bindings
 apk update && apk add elektra elektra-python py3-elektra
 ```
 
 Under regular alpine, you have to install python3 from the edge repository. If you do not want to add the edge repositories permanently like above, you can do
 
 ```sh
-apk add --repository "http://dl-cdn.alpinelinux.org/alpine/edge/main" python3
-apk add --repository "http://dl-cdn.alpinelinux.org/alpine/edge/testing" elektra elektra-python py3-elektra
+apk add --repository "https://dl-cdn.alpinelinux.org/alpine/edge/main" python3
+apk add --repository "https://dl-cdn.alpinelinux.org/alpine/edge/testing" elektra elektra-python py3-elektra
 ```
 
 ### Debian

diff --git a/src/tools/website/README.md b/src/tools/website/README.md
@@ -10,7 +10,7 @@ The website is developed as a single-page application (SPA) in [AngularJS (v1.5)
 All dependencies are either already contained in the application project or (preferred) resolved through
 the dependency manager [npm](https://www.npmjs.com/) during installation (requires active internet connection).
 Compiling (browserification, concatenation & minification), as well as other tasks like running a lightweight
-webserver are handled by the nodeJS based task runner [grunt](http://gruntjs.com/) (installed by npm).
+webserver are handled by the nodeJS based task runner [grunt](https://gruntjs.com/) (installed by npm).
 
 ## Run and Configure
 
@@ -168,7 +168,7 @@ This field type supports following attributes:
 
 - `name` (string) for the visible name of the menu point (i.e. button text)
 - `ref` (string) for the dynamic URL part (i.e. a resource of the URL,
-  e.g. `http://example.com/docs` for the subsequent example)
+  e.g. `https://example.com/docs` for the subsequent example)
 - `children` (array) holding other structure elements, but none of type `submenu`
 
 Example:
@@ -192,7 +192,7 @@ This field type support following attributes:
 
 - `name` (string) for the visible name of the menu point (i.e. button text)
 - `ref` (string) for the dynamic URL part (i.e. a resource of the URL,
-  e.g. `http://example.com/plugins` for the subsequent example)
+  e.g. `https://example.com/plugins` for the subsequent example)
 - `options` (object) with further options:
   - `path` (string) containing the path from the repository root to the text file to parse
   - `target_file` (array[string]) containing some filenames that should be
@@ -245,7 +245,7 @@ This field type supports following attributes:
 
 - `name` (string) for the visible name of the menu point (i.e. button text)
 - `ref` (string) for the dynamic URL part (i.e. a resource of the URL,
-  e.g. `http://example.com/tools` for the subsequent example)
+  e.g. `https://example.com/tools` for the subsequent example)
 - `options` (object) with further options:
   - `path` (string) containing the path from the repository root to the directory to enumerate
   - `target_file` (array[string]) containing some filenames that should be targeted within the sub-directories
@@ -275,7 +275,7 @@ This field type supports following attributes:
 
 - `name` (string) for the visible name of the menu point (i.e. button text)
 - `ref` (string) for the dynamic URL part (i.e. a resource of the URL,
-  e.g. `http://example.com/man-pages` for the subsequent example)
+  e.g. `https://example.com/man-pages` for the subsequent example)
 - `options` (object) with further options:
   - `path` (string) containing the path from the repository root to the directory to enumerate
   - `blacklist` (array[string]) containing some filenames that should
@@ -305,7 +305,7 @@ This field type supports following attributes:
 
 - `name` (string) for the visible name of the menu point (i.e. button text)
 - `ref` (string) for the dynamic URL part (i.e. a resource of the URL,
-  e.g. `http://example.com/getstarted` for the subsequent example)
+  e.g. `https://example.com/getstarted` for the subsequent example)
 - `children` (array) holding static structure elements like `staticref`, `staticfile` and `link`
 
 Example:
-Original file line number
+Diff line change
@@ Expand Up @@
     #> …
     ```
-    . We can also use the log file to create a [Flame Graph](http://www.brendangregg.com/flamegraphs.html). To do that we use the `llvm-xray stack` to create an input file for the tool [`flamegraph.pl`][flamegraph]
+    . We can also use the log file to create a [Flame Graph](https://www.brendangregg.com/flamegraphs.html). To do that we use the `llvm-xray stack` to create an input file for the tool [`flamegraph.pl`][flamegraph]
     ```sh
     llvm-xray stack "$LOGFILE" -stack-format=flame -aggregation-type=time -all-stacks \
@@ Expand Down @@