Replace http with https whenever possible (phoenixframework#4577)

* Replace http with https whenever possible

* Apply suggestions from code review

I agree @mcrumm

Co-authored-by: Michael Crumm <[email protected]>

Co-authored-by: Michael Crumm <[email protected]>

CODE_OF_CONDUCT.md

@@ -19,4 +19,4 @@ This code of conduct applies both within project spaces and in public spaces whe
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
 
-This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.2.0, available at [http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.2.0, available at [https://www.contributor-covenant.org/version/1/2/0/code-of-conduct/](https://www.contributor-covenant.org/version/1/2/0/code-of-conduct/)

CONTRIBUTING.md

@@ -13,11 +13,11 @@ Use the issues tracker for:
 
 Please **do not** use the issue tracker for personal support requests nor feature requests. Support requests should be sent to:
 
-* The [phoenix-talk mailing list](http://groups.google.com/group/phoenix-talk) (closed in favor of forum, but archive is still online)
+* The [phoenix-talk mailing list](https://groups.google.com/group/phoenix-talk) (closed in favor of forum, but archive is still online)
 * [The Phoenix subforum on the Elixir forum](https://elixirforum.com/c/phoenix-forum)
 * **[#elixir](irc://irc.libera.chat/elixir)** on [Libera](https://libera.chat/) IRC
 
-Development issues can be discussed on the [phoenix-core mailing list](http://groups.google.com/group/phoenix-core).
+Development issues can be discussed on the [phoenix-core mailing list](https://groups.google.com/group/phoenix-core).
 
 We do our best to keep the issue tracker tidy and organized, making it useful
 for everyone. For example, we classify open issues per perceived difficulty,
@@ -65,7 +65,7 @@ Example:
 
 ## Feature requests
 
-Feature requests are welcome and should be discussed on the [phoenix-core mailing list](http://groups.google.com/group/phoenix-core). But take a moment to find
+Feature requests are welcome and should be discussed on the [phoenix-core mailing list](https://groups.google.com/group/phoenix-core). But take a moment to find
 out whether your idea fits with the scope and aims of the project. It's up to *you*
 to make a strong case to convince the community of the merits of this feature.
 Please provide as much detail and context as possible.

README.md

@@ -86,7 +86,7 @@ $ npm run watch
   [3]: https://elixir-slackin.herokuapp.com/
   [4]: https://github.com/phoenixframework/phoenix/issues
   [5]: https://elixirforum.com/c/phoenix-forum
-  [6]: http://groups.google.com/group/phoenix-core
+  [6]: https://groups.google.com/group/phoenix-core
 
 ## Copyright and License
 

guides/ecto.md

@@ -577,7 +577,7 @@ $ mix ecto.migrate
 
 ## Other options
 
-While Phoenix uses the `Ecto` project to interact with the data access layer, there are many other data access options, some even built into the Erlang standard library. [ETS](http://www.erlang.org/doc/man/ets.html) – available in Ecto via [`etso`](https://hexdocs.pm/etso/) – and [DETS](http://www.erlang.org/doc/man/dets.html) are key-value data stores built into [OTP](http://www.erlang.org/doc/). OTP also provides a relational database called [Mnesia](http://www.erlang.org/doc/man/mnesia.html) with its own query language called QLC. Both Elixir and Erlang also have a number of libraries for working with a wide range of popular data stores.
+While Phoenix uses the `Ecto` project to interact with the data access layer, there are many other data access options, some even built into the Erlang standard library. [ETS](https://www.erlang.org/doc/man/ets.html) – available in Ecto via [`etso`](https://hexdocs.pm/etso/) – and [DETS](https://www.erlang.org/doc/man/dets.html) are key-value data stores built into [OTP](https://www.erlang.org/doc/). OTP also provides a relational database called [Mnesia](https://www.erlang.org/doc/man/mnesia.html) with its own query language called QLC. Both Elixir and Erlang also have a number of libraries for working with a wide range of popular data stores.
 
 The data world is your oyster, but we won't be covering these options in these guides.
 

guides/howto/using_ssl.md

@@ -31,7 +31,7 @@ Without the `otp_app:` key, we need to provide absolute paths to the files where
 Path.expand("../../../some/path/to/ssl/key.pem", __DIR__)
 ```
 
-The options under the `https:` key are passed to the Plug adapter, typically `Plug.Cowboy`, which in turn uses `Plug.SSL` to select the TLS socket options. Please refer to the documentation for [Plug.SSL.configure/1](https://hexdocs.pm/plug/Plug.SSL.html#configure/1) for more information on the available options and their defaults. The [Plug HTTPS Guide](https://hexdocs.pm/plug/https.html) and the [Erlang/OTP ssl](http://erlang.org/doc/man/ssl.html) documentation also provide valuable information.
+The options under the `https:` key are passed to the Plug adapter, typically `Plug.Cowboy`, which in turn uses `Plug.SSL` to select the TLS socket options. Please refer to the documentation for [Plug.SSL.configure/1](https://hexdocs.pm/plug/Plug.SSL.html#configure/1) for more information on the available options and their defaults. The [Plug HTTPS Guide](https://hexdocs.pm/plug/https.html) and the [Erlang/OTP ssl](https://erlang.org/doc/man/ssl.html) documentation also provide valuable information.
 
 ## SSL in Development
 

guides/introduction/community.md

@@ -12,7 +12,7 @@ There are a number of places to connect with community members at all experience
 
   * Read about [bug reports](https://github.com/phoenixframework/phoenix/blob/master/CONTRIBUTING.md#bug-reports) or open an issue in the Phoenix [issue tracker](https://github.com/phoenixframework/phoenix/issues).
 
-  * Ask or answer questions about Phoenix on [Elixir Forum](https://elixirforum.com/c/phoenix-forum) or [Stack Overflow](http://stackoverflow.com/questions/tagged/phoenix-framework).
+  * Ask or answer questions about Phoenix on [Elixir Forum](https://elixirforum.com/c/phoenix-forum) or [Stack Overflow](https://stackoverflow.com/questions/tagged/phoenix-framework).
 
   * To discuss new features in the framework, email the [phoenix-core mailing list](https://groups.google.com/group/phoenix-core).
 

guides/real_time/channels.md

@@ -159,7 +159,7 @@ This is useful to broadcast messages on channel and also for application develop
 The PubSub system takes care of getting messages from one node to another so that they can be sent to all subscribers across the cluster.
 By default, this is done using [Phoenix.PubSub.PG2](https://hexdocs.pm/phoenix_pubsub/Phoenix.PubSub.PG2.html), which uses native BEAM messaging.
 
-If your deployment environment does not support distributed Elixir or direct communication between servers, Phoenix also ships with a [Redis Adapter](https://hexdocs.pm/phoenix_pubsub_redis/Phoenix.PubSub.Redis.html) that uses Redis to exchange PubSub data. Please see the [Phoenix.PubSub docs](http://hexdocs.pm/phoenix_pubsub/Phoenix.PubSub.html) for more information.
+If your deployment environment does not support distributed Elixir or direct communication between servers, Phoenix also ships with a [Redis Adapter](https://hexdocs.pm/phoenix_pubsub_redis/Phoenix.PubSub.Redis.html) that uses Redis to exchange PubSub data. Please see the [Phoenix.PubSub docs](https://hexdocs.pm/phoenix_pubsub/Phoenix.PubSub.html) for more information.
 
 ### Client Libraries
 
@@ -481,4 +481,4 @@ Phoenix uses an at-most-once strategy when sending messages to clients. If the c
 
 To see an example of the application we just built, checkout the project [phoenix_chat_example](https://github.com/chrismccord/phoenix_chat_example).
 
-You can also see a live demo at <http://phoenixchat.herokuapp.com/>.
+You can also see a live demo at <https://phoenixchat.herokuapp.com/>.

guides/real_time/presence.md

@@ -35,7 +35,7 @@ in lib/hello/application.ex:
     ]
 
 You're all set! See the Phoenix.Presence docs for more details:
-http://hexdocs.pm/phoenix/Phoenix.Presence.html
+https://hexdocs.pm/phoenix/Phoenix.Presence.html
 ```
 
 If we open up the `lib/hello_web/channels/presence.ex` file, we will see the following line:

guides/telemetry.md

@@ -31,7 +31,7 @@ defines a `metrics/0` function, which returns a list of
 that you define for your application.
 
 By default, the supervisor also starts
-[`:telemetry_poller`](http://hexdocs.pm/telemetry_poller).
+[`:telemetry_poller`](https://hexdocs.pm/telemetry_poller).
 By simply adding `:telemetry_poller` as a dependency, you
 can receive VM-related events on a specified interval.
 
@@ -111,7 +111,7 @@ children = [
 ## Telemetry Events
 
 Many Elixir libraries (including Phoenix) are already using
-the [`:telemetry`](http://hexdocs.pm/telemetry) package as a
+the [`:telemetry`](https://hexdocs.pm/telemetry) package as a
 way to give users more insight into the behavior of their
 applications, by emitting events at key moments in the
 application lifecycle.
@@ -455,7 +455,7 @@ event.
 
 You might want to periodically measure key-value pairs within
 your application. Fortunately the
-[`:telemetry_poller`](http://hexdocs.pm/telemetry_poller)
+[`:telemetry_poller`](https://hexdocs.pm/telemetry_poller)
 package provides a mechanism for custom measurements,
 which is useful for retrieving process information or for
 performing custom measurements periodically.

installer/lib/mix/tasks/phx.new.ex

@@ -97,7 +97,7 @@ defmodule Mix.Tasks.Phx.New do
   ```
 
   You can read more about umbrella projects using the
-  official [Elixir guide](http://elixir-lang.org/getting-started/mix-otp/dependencies-and-umbrella-apps.html#umbrella-projects)
+  official [Elixir guide](https://elixir-lang.org/getting-started/mix-otp/dependencies-and-umbrella-apps.html#umbrella-projects)
   """
   use Mix.Task
   alias Phx.New.{Generator, Project, Single, Umbrella, Web, Ecto}

installer/templates/phx_live/assets/topbar.js

@@ -1,7 +1,7 @@
 /**
  * @license MIT
  * topbar 1.0.0, 2021-01-06
- * http://buunguyen.github.io/topbar
+ * https://buunguyen.github.io/topbar
  * Copyright (c) 2021 Buu Nguyen
  */
 (function (window, document) {

installer/templates/phx_static/robots.txt

@@ -1,4 +1,4 @@
-# See http://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file
+# See https://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file
 #
 # To ban all spiders from the entire site uncomment the next two lines:
 # User-agent: *

lib/mix/tasks/phx.gen.presence.ex

@@ -51,7 +51,7 @@ defmodule Mix.Tasks.Phx.Gen.Presence do
         ]
 
     You're all set! See the Phoenix.Presence docs for more details:
-    http://hexdocs.pm/phoenix/Phoenix.Presence.html
+    https://hexdocs.pm/phoenix/Phoenix.Presence.html
     """
   end
 

lib/phoenix/controller.ex

@@ -392,7 +392,7 @@ defmodule Phoenix.Controller do
 
       iex> redirect(conn, to: "/login")
 
-      iex> redirect(conn, external: "http://elixir-lang.org")
+      iex> redirect(conn, external: "https://elixir-lang.org")
 
   """
   def redirect(conn, opts) when is_list(opts) do

lib/phoenix/router.ex

@@ -220,7 +220,7 @@ defmodule Phoenix.Router do
   request is dispatched to a desired end-point.
 
   Such transformations are defined via plugs, as defined
-  in the [Plug](http://github.com/elixir-lang/plug) specification.
+  in the [Plug](https://github.com/elixir-lang/plug) specification.
   Once a pipeline is defined, it can be piped through per scope.
 
   For example:

priv/templates/phx.gen.presence/presence.ex

@@ -2,7 +2,7 @@ defmodule <%= module %> do
   @moduledoc """
   Provides presence tracking to channels and processes.
 
-  See the [`Phoenix.Presence`](http://hexdocs.pm/phoenix/Phoenix.Presence.html)
+  See the [`Phoenix.Presence`](https://hexdocs.pm/phoenix/Phoenix.Presence.html)
   docs for more details.
   """
   use Phoenix.Presence, otp_app: <%= inspect otp_app %>,