Setting up the Apache HTTP Server with a Rocket application

We know that Rocket has TLS support in its configuration, so we can set the TCP port to 443, the default HTTPS connection port. In some cases, it might be acceptable to run web applications directly, for example, when we want to serve content for microservices.

One of the reasons why we don't want to run the Rocket application directly is because of this warning in the Rocket guide:

Rocket's built-in TLS implements only TLS 1.2 and 1.3. It may not be suitable for production use.

The TLS library used by the Rocket framework might not be suitable for production use for various reasons, such as security reasons or it is not yet audited.

There are other reasons why we do not want to serve content directly from Rocket aside from the TLS library problem. One example is when we want to serve multiple applications from a single computer. We might want to serve PHP applications from the same machine too.

One...