Replace http:// with https:// where applicable

The testcases will be updated automatically in a separate commit.

.github/CONTRIBUTING.md

@@ -6,7 +6,7 @@ Note that bug reports and feature requests for related projects should be filed
 
 ## i3 bug reports and feature requests
 
-1. Read the [debugging instructions](http://i3wm.org/docs/debugging.html).
+1. Read the [debugging instructions](https://i3wm.org/docs/debugging.html).
 2. Make sure you include a link to your logfile in your report (section 3).
 3. Make sure you include the i3 version number in your report (section 1).
 4. Please be aware that we cannot support compatibility issues with
@@ -25,11 +25,11 @@ Note that bug reports and feature requests for related projects should be filed
   ”feature request” or ”enhancement” in its title.
 * Use the `next` branch for developing and sending your pull request.
 * Use `clang-format` to format your code.
-* Run the [testsuite](http://i3wm.org/docs/testsuite.html)
+* Run the [testsuite](https://i3wm.org/docs/testsuite.html)
 
 ## Finding something to do
 
 * Find a [reproducible bug](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Areproducible+label%3Abug+) from the issue tracker. These issues have been reviewed and confirmed by a project contributor.
 * Find an [accepted enhancement](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Aaccepted+label%3Aenhancement) from the issue tracker. These have been approved and are ok to start working on.
 
-There's a very good [overview of the codebase](http://i3wm.org/docs/hacking-howto.html) available to get you started.
+There's a very good [overview of the codebase](https://i3wm.org/docs/hacking-howto.html) available to get you started.

.github/ISSUE_TEMPLATE.md

@@ -2,7 +2,7 @@ Output of `i3 --moreversion 2>&- || i3 --version`:
 
 _REPLACE: i3 version output_
 
-URL to a logfile as per http://i3wm.org/docs/debugging.html:
+URL to a logfile as per https://i3wm.org/docs/debugging.html:
 
 _REPLACE: URL to logfile_
 

AnyEvent-I3/Makefile.PL

@@ -23,7 +23,7 @@ my %meta = (
             web => 'https://github.com/i3/i3/issues',
         },
         homepage => 'https://i3wm.org/',
-        license  => ['http://dev.perl.org/licenses'],
+        license  => ['https://dev.perl.org/licenses'],
     },
 );
 

AnyEvent-I3/README

@@ -23,10 +23,10 @@ perldoc command.
 You can also look for information at:
 
     RT, CPAN's request tracker
-        http://rt.cpan.org/NoAuth/Bugs.html?Dist=AnyEvent-I3
+        https://rt.cpan.org/NoAuth/Bugs.html?Dist=AnyEvent-I3
 
     The i3 window manager website
-        http://i3.zekjur.net/
+        https://i3wm.org
 
 
 LICENSE AND COPYRIGHT
@@ -37,4 +37,4 @@ This program is free software; you can redistribute it and/or modify it
 under the terms of either: the GNU General Public License as published
 by the Free Software Foundation; or the Artistic License.
 
-See http://dev.perl.org/licenses/ for more information.
+See https://dev.perl.org/licenses/ for more information.

AnyEvent-I3/lib/AnyEvent/I3.pm

@@ -543,7 +543,7 @@ Michael Stapelberg, C<< <michael at i3wm.org> >>
 
 Please report any bugs or feature requests to C<bug-anyevent-i3 at
 rt.cpan.org>, or through the web interface at
-L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=AnyEvent-I3>.  I will be
+L<https://rt.cpan.org/NoAuth/ReportBug.html?Queue=AnyEvent-I3>.  I will be
 notified, and then you'll automatically be notified of progress on your bug as
 I make changes.
 
@@ -559,11 +559,11 @@ You can also look for information at:
 
 =item * RT: CPAN's request tracker
 
-L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=AnyEvent-I3>
+L<https://rt.cpan.org/NoAuth/Bugs.html?Dist=AnyEvent-I3>
 
 =item * The i3 window manager website
 
-L<http://i3wm.org>
+L<https://i3wm.org>
 
 =back
 
@@ -579,7 +579,7 @@ This program is free software; you can redistribute it and/or modify it
 under the terms of either: the GNU General Public License as published
 by the Free Software Foundation; or the Artistic License.
 
-See http://dev.perl.org/licenses/ for more information.
+See https://dev.perl.org/licenses/ for more information.
 
 
 =cut

DEPENDS

@@ -7,29 +7,29 @@
 ┌──────────────┬────────┬────────┬───────────────────────────────────────────────────────────┐
 │ dependency   │ min.   │ lkgv   │ URL                                                       │
 ├──────────────┼────────┼────────┼───────────────────────────────────────────────────────────┤
-│ pkg-config   │ 0.25   │ 0.29   │ http://pkgconfig.freedesktop.org/                         │
-│ libxcb       │ 1.1.93 │ 1.12   │ http://xcb.freedesktop.org/dist/                          │
-│ xcb-util     │ 0.3.3  │ 0.4.1  │ http://xcb.freedesktop.org/dist/                          │
-│ xkbcommon    │ 0.4.0  │ 0.6.1  │ http://xkbcommon.org/                                     │
-│ xkbcommon-x11│ 0.4.0  │ 0.6.1  │ http://xkbcommon.org/                                     │
-│ util-cursor³⁴│ 0.0.99 │ 0.1.3  │ http://xcb.freedesktop.org/dist/                          │
-│ util-wm⁴     │ 0.3.8  │ 0.3.8  │ http://xcb.freedesktop.org/dist/                          │
-│ util-keysyms⁴│ 0.3.8  │ 0.4.0  │ http://xcb.freedesktop.org/dist/                          │
+│ pkg-config   │ 0.25   │ 0.29   │ https://pkgconfig.freedesktop.org/                        │
+│ libxcb       │ 1.1.93 │ 1.12   │ https://xcb.freedesktop.org/dist/                         │
+│ xcb-util     │ 0.3.3  │ 0.4.1  │ https://xcb.freedesktop.org/dist/                         │
+│ xkbcommon    │ 0.4.0  │ 0.6.1  │ https://xkbcommon.org/                                    │
+│ xkbcommon-x11│ 0.4.0  │ 0.6.1  │ https://xkbcommon.org/                                    │
+│ util-cursor³⁴│ 0.0.99 │ 0.1.3  │ https://xcb.freedesktop.org/dist/                         │
+│ util-wm⁴     │ 0.3.8  │ 0.3.8  │ https://xcb.freedesktop.org/dist/                         │
+│ util-keysyms⁴│ 0.3.8  │ 0.4.0  │ https://xcb.freedesktop.org/dist/                         │
 │ util-xrm⁴    │ 1.0.0  │ 1.0.0  │ https://github.com/Airblader/xcb-util-xrm                 │
 │ libev        │ 4.0    │ 4.19   │ http://libev.schmorp.de/                                  │
-│ yajl         │ 2.0.1  │ 2.1.0  │ http://lloyd.github.com/yajl/                             │
+│ yajl         │ 2.0.1  │ 2.1.0  │ https://lloyd.github.com/yajl/                            │
 │ asciidoc     │ 8.3.0  │ 8.6.9  │ http://www.methods.co.nz/asciidoc/                        │
 │ xmlto        │ 0.0.23 │ 0.0.23 │ http://www.methods.co.nz/asciidoc/                        │
 │ Pod::Simple² │ 3.22   │ 3.22   │ http://search.cpan.org/~dwheeler/Pod-Simple-3.23/         │
 │ docbook-xml  │ 4.5    │ 4.5    │ http://www.methods.co.nz/asciidoc/                        │
-│ PCRE         │ 8.12   │ 8.38   │ http://www.pcre.org/                                      │
-│ libsn¹       │ 0.10   │ 0.12   │ http://freedesktop.org/wiki/Software/startup-notification │
+│ PCRE         │ 8.12   │ 8.38   │ https://www.pcre.org/                                     │
+│ libsn¹       │ 0.10   │ 0.12   │ https://freedesktop.org/wiki/Software/startup-notification │
 │ pango        │ 1.30.0 | 1.40.1 │ http://www.pango.org/                                     │
-│ cairo        │ 1.14.4 │ 1.14.6 │ http://cairographics.org/                                 │
+│ cairo        │ 1.14.4 │ 1.14.6 │ https://cairographics.org/                                │
 └──────────────┴────────┴────────┴───────────────────────────────────────────────────────────┘
  ¹ libsn = libstartup-notification
  ² Pod::Simple is a Perl module required for converting the testsuite
-   documentation to HTML. See http://michael.stapelberg.de/cpan/#Pod::Simple
+   documentation to HTML. See https://michael.stapelberg.de/cpan/#Pod::Simple
  ³ xcb-util-cursor, to be precise.
  ⁴ Depending on your distribution, this might be considered part of xcb-util.
 

contrib/per-workspace-layout.pl

@@ -1,7 +1,7 @@
 #!/usr/bin/env perl
 # vim:ts=4:sw=4:expandtab
 # © 2012 Michael Stapelberg
-# Licensed under BSD license, see http://code.i3wm.org/i3/tree/LICENSE
+# Licensed under BSD license, see https://github.com/i3/i3/blob/next/LICENSE
 #
 # Append this line to your i3 config file:
 #     exec_always ~/per-workspace-layout.pl

debian/control

@@ -27,7 +27,7 @@ Build-Depends: debhelper (>= 9),
                libpango1.0-dev,
                libpod-simple-perl
 Standards-Version: 3.9.8
-Homepage: http://i3wm.org/
+Homepage: https://i3wm.org/
 
 Package: i3
 Architecture: any

debian/copyright

@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: i3
 Upstream-Contact: Michael Stapelberg <michael@i3wm.org>
 Source: https://i3wm.org/

docs/asciidoc-git.conf

@@ -520,8 +520,8 @@ cellspacing="0" cellpadding="4">
 
 [header]
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
-    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="{lang=en}">
+    "https://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="https://www.w3.org/1999/xhtml" xml:lang="{lang=en}">
 <head>
 <link rel="icon" type="image/png" href="/favicon.png">
 <meta http-equiv="Content-Type" content="{quirks=application/xhtml+xml}{quirks?text/html}; charset={encoding}" />
@@ -647,7 +647,7 @@ endif::doctype-manpage[]
 </div>
 {disable-javascript%<div id="footnotes"><hr /></div>}
 <div id="footer" lang="de">
-© 2009 Michael Stapelberg, <a href="http://i3wm.org/impress.html">Impressum</a>
+© 2009 Michael Stapelberg, <a href="https://i3wm.org/impress.html">Impressum</a>
 </div>
 </body>
 </html>

docs/debugging

@@ -32,8 +32,8 @@ if you can.
 
 4.7-85-g9c15b95 (development version)::
 Your version is 85 commits newer than 4.7, and the git revision of your
-version is +9c15b95+. Go to http://code.i3wm.org/i3/commit/?h=next and see if
-the line "commit" starts with the same revision. If so, you are using the
+version is +9c15b95+. Go to https://github.com/i3/i3/commits/next and see if
+the most recent commit starts with the same revision. If so, you are using the
 latest version.
 
 Development versions of i3 have logging enabled by default and are compiled
@@ -109,9 +109,9 @@ No matter whether i3 misbehaved in some way without crashing or whether it just
 crashed, the logfile provides all information necessary to debug the problem.
 
 To upload a compressed version of the logfile (for a bugreport), use:
-------------------------------------------------------------------------------
-DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- http://logs.i3wm.org
-------------------------------------------------------------------------------
+-------------------------------------------------------------------------------
+DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- https://logs.i3wm.org
+-------------------------------------------------------------------------------
 
 This command does not depend on i3 (it also works while i3 displays
 the crash dialog), but it requires a working X11 connection.
@@ -154,9 +154,9 @@ you found the section which clearly highlights the problem, additional
 information might be necessary to completely diagnose the problem.
 
 When debugging with us in IRC, be prepared to use a so called nopaste service
-such as http://nopaste.info or http://pastebin.com because pasting large
-amounts of text in IRC sometimes leads to incomplete lines (servers have line
-length limitations) or flood kicks.
+such as https://pastebin.com because pasting large amounts of text in IRC
+sometimes leads to incomplete lines (servers have line length limitations) or
+flood kicks.
 
 == Debugging i3bar
 

docs/hacking-howto

@@ -52,8 +52,8 @@ Here’s a memory refresher:
 == Using git / sending patches
 
 For a short introduction into using git, see
-http://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_the_lazy
-or, for more documentation, see http://git-scm.com/documentation
+https://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_the_lazy
+or, for more documentation, see https://git-scm.com/documentation
 
 Please talk to us before working on new features to see whether they will be
 accepted. A good way for this is to open an issue and asking for opinions on it.
@@ -156,7 +156,7 @@ workspace, the split container we are talking about is the workspace.
 
 To get an impression of how different layouts are represented, just play around
 and look at the data structures -- they are exposed as a JSON hash. See
-http://i3wm.org/docs/ipc.html#_tree_reply for documentation on that and an
+https://i3wm.org/docs/ipc.html#_tree_reply for documentation on that and an
 example.
 
 == Files

docs/i3-pod2html

@@ -31,7 +31,7 @@ $parser->html_header_before_title(
 <meta charset="utf-8">
 <meta name="generator" content="Pod::Simple::HTML">
 <meta name="description" content="i3 Perl documentation">
-<link rel="stylesheet" href="http://i3wm.org/css/style.css" type="text/css" />
+<link rel="stylesheet" href="https://i3wm.org/css/style.css" type="text/css" />
 <style type="text/css">
 .pod pre {
     background: #333;
@@ -75,9 +75,9 @@ $parser->html_header_after_title(
 			<ul id="nav">
 				<li><a style="border-bottom: 2px solid #fff" href="/docs">Docs</a></li>
 				<li><a href="/screenshots">Screens</a></li>
-				<li><a href="http://faq.i3wm.org/">FAQ</a></li>
+				<li><a href="https://www.reddit.com/r/i3wm/">FAQ</a></li>
 				<li><a href="/contact">Contact</a></li>
-				<li><a href="http://bugs.i3wm.org/">Bugs</a></li>
+				<li><a href="https://bugs.i3wm.org/">Bugs</a></li>
 			</ul>
 	<br style="clear: both">
 <div id="content" class="pod">

docs/i3bar-protocol

@@ -96,7 +96,7 @@ i3status and others will output single statuslines in one line, separated by
 
 You can find an example of a shell script which can be used as your
 +status_command+ in the bar configuration at
-http://code.stapelberg.de/git/i3/tree/contrib/trivial-bar-script.sh?h=next
+https://github.com/i3/i3/blob/next/contrib/trivial-bar-script.sh
 
 === Header in detail
 

docs/layout-saving

@@ -52,7 +52,7 @@ it will be placed in the corresponding placeholder window. We say it gets
 
 Note: Swallowing windows into unsatisfied placeholder windows takes precedence
 over
-link:http://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces[assignment
+link:https://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces[assignment
 rules]. For example, if you assign all Emacs windows to workspace 1 in your i3
 configuration file, but there is a placeholder window on workspace 2 which
 matches Emacs as well, your newly started Emacs window will end up in the
@@ -164,7 +164,7 @@ a Chrome window:
 image:layout-saving-1.png["Restored layout",width=400,link="layout-saving-1.png"]
 
 The structure of this JSON file looks a lot like the +TREE+ reply, see
-http://build.i3wm.org/docs/ipc.html#_tree_reply for documentation on that. Some
+https://build.i3wm.org/docs/ipc.html#_tree_reply for documentation on that. Some
 properties are excluded because they are not relevant when restoring a layout.
 
 Most importantly, look at the "swallows" section of each window. This is where
@@ -229,8 +229,8 @@ Both deviations from the JSON standard are to make manual editing by humans
 easier. In case you are writing a more elaborate tool for manipulating these
 layouts, you can either use a JSON parser that supports these deviations (for
 example libyajl), transform the layout file to a JSON-conforming file, or
-link:http://cr.i3wm.org/[submit a patch] to make +i3-save-tree(1)+ optionally
-output standard-conforming JSON.
+link:https://github.com/i3/i3/blob/next/.github/CONTRIBUTING.md[submit a patch]
+to make +i3-save-tree(1)+ optionally output standard-conforming JSON.
 
 == Troubleshooting
 

docs/refcard.html

@@ -34,7 +34,7 @@
 	<header>
 		<img id="logo" src="logo-30.png" alt="" />
 		<h1>i3 Reference Card</h1>
-		<a href="http://i3wm.org/docs/userguide.html">http://i3wm.org/docs/userguide.html</a>
+		<a href="https://i3wm.org/docs/userguide.html">https://i3wm.org/docs/userguide.html</a>
 		<p>
 			Throughout this guide, the i3 logo will be used to refer to the configured modifier.
 			This is the <kbd></kbd> key (<code>Mod1</code>) by default,

docs/testsuite

@@ -41,10 +41,10 @@ Apart from this document, you should also have a look at:
    http://onyxneon.com/books/modern_perl/modern_perl_a4.pdf
 2. The latest Perl documentation of the "i3test" (general testcase setup) and
    "i3test::Test" (additional test instructions) modules:
-   http://build.i3wm.org/docs/lib-i3test.html respectively
-   http://build.i3wm.org/docs/lib-i3test-test.html
+   https://build.i3wm.org/docs/lib-i3test.html respectively
+   https://build.i3wm.org/docs/lib-i3test-test.html
 3. The latest documentation on i3’s IPC interface:
-   http://build.i3wm.org/docs/ipc.html
+   https://build.i3wm.org/docs/ipc.html
 
 == Implementation
 
@@ -99,7 +99,7 @@ $ sudo cpan .
 --------------------------------------------------------------------------------
 
 In case you don’t have root permissions, you can also install into your home
-directory, see http://michael.stapelberg.de/cpan/
+directory, see https://michael.stapelberg.de/cpan/
 
 === Mechanisms
 
@@ -240,7 +240,7 @@ interface which i3 provides. It is used for the startup process of i3, for
 terminating it cleanly and (most importantly) for modifying and getting the
 current state (layout tree).
 
-See [http://i3wm.org/docs/ipc.html] for documentation on the IPC interface.
+See [https://i3wm.org/docs/ipc.html] for documentation on the IPC interface.
 
 ==== X11::XCB
 

docs/userguide

@@ -802,7 +802,7 @@ The first part of the WM_CLASS is the instance ("irssi" in this example), the
 second part is the class ("URxvt" in this example).
 
 Should you have any problems with assignments, make sure to check the i3
-logfile first (see http://i3wm.org/docs/debugging.html). It includes more
+logfile first (see https://i3wm.org/docs/debugging.html). It includes more
 details about the matching process and the window’s actual class, instance and
 title when starting up.
 
@@ -1056,7 +1056,7 @@ force_focus_wrapping yes
 
 === Forcing Xinerama
 
-As explained in-depth in <http://i3wm.org/docs/multi-monitor.html>, some X11
+As explained in-depth in <https://i3wm.org/docs/multi-monitor.html>, some X11
 video drivers (especially the nVidia binary driver) only provide support for
 Xinerama instead of RandR. In such a situation, i3 must be told to use the
 inferior Xinerama API explicitly and therefore don’t provide support for
@@ -2448,7 +2448,7 @@ bindsym $mod+u border none
 [[shmlog]]
 === Enabling shared memory logging
 
-As described in http://i3wm.org/docs/debugging.html, i3 can log to a shared
+As described in https://i3wm.org/docs/debugging.html, i3 can log to a shared
 memory buffer, which you can dump using +i3-dump-log+. The +shmlog+ command
 allows you to enable or disable the shared memory logging at runtime.
 

docs/wsbar

@@ -48,7 +48,7 @@ will be adjusted properly.
 
 +i3-wsbar+ used to be the reference implementation before we had +i3bar+.
 Nowadays, it is not shipped with release tarballs, but you can still get it at
-http://code.stapelberg.de/git/i3/tree/contrib/i3-wsbar
+https://github.com/i3/i3/blob/next/contrib/i3-wsbar
 
 === The big picture
 

etc/config

@@ -1,6 +1,6 @@
 # i3 config file (v4)
 #
-# Please see http://i3wm.org/docs/userguide.html for a complete reference!
+# Please see https://i3wm.org/docs/userguide.html for a complete reference!
 #
 # This config file uses keycodes (bindsym) and was written for the QWERTY
 # layout.

etc/config.keycodes

@@ -6,7 +6,7 @@
 
 # i3 config file (v4)
 #
-# Please see http://i3wm.org/docs/userguide.html for a complete reference!
+# Please see https://i3wm.org/docs/userguide.html for a complete reference!
 
 set $mod Mod1