## Let's Encrypt

Avant Let's Encrypt, ces certificats HTTPS étaient vendus par des tiers de confiance.

        assertNotNull(Curl.head("https://cdn.example.com/assets/file.js"));
        assertNotNull(Curl.options("http://cors.example.com/api"));
        assertNotNull(Curl.connect("http://proxy.example.com:3128"));
    }

    @Test
    public void test_HttpMethodEnumValues() {
        // ## Test that all expected HTTP methods are present in the enum ##

        // ## Act ##

        webSocketListener = listener
      }

    /**
     * Configures this response to be served as a response to an HTTP CONNECT request, either for
     * doing HTTPS through an HTTP proxy, or HTTP/2 prior knowledge through an HTTP proxy.
     *
     * When a new connection is received, all in-tunnel responses are served before the connection is
     * upgraded to HTTPS or HTTP/2.
     */
    public fun inTunnel(): Builder =

    * [metatada-proxy addon] Bump prometheus-to-sd v0.5.0 to pick up security fixes.

And there has to be something in charge of **renewing the HTTPS certificates**, it could be the same component or it could be something different.

### Example Tools for HTTPS { #example-tools-for-https }

Some of the tools you could use as a TLS Termination Proxy are:

* Traefik
    * Automatically handles certificates renewals ✨
* Caddy

# Virtual Host: Host:fess.codelibs.org=fess
virtual.host.headers=

# Hostname for the HTTP proxy server.
http.proxy.host=
# Port number for the HTTP proxy server (e.g., 8080).
http.proxy.port=8080
# Username for HTTP proxy authentication.
http.proxy.username=
# Password for HTTP proxy authentication.
http.proxy.password=
# Maximum size (bytes) for HTTP file uploads.
http.fileupload.max.size=262144000

In most cases you would (and should) have a "termination proxy" handling HTTPS for you on top, this will depend on how you deploy your application, your provider might do this for you, or you might need to set it up yourself.

/// tip

En la mayoría de los casos tendrías (y deberías) tener un "proxy de terminación" manejando HTTPS por ti, esto dependerá de cómo despliegues tu aplicación, tu proveedor podría hacer esto por ti, o podrías necesitar configurarlo tú mismo.

/// tip | Consejo

////

/// tip | Consejo

Podrías usar la misma técnica para extender el JSON Schema y añadir tu propia información extra personalizada.

Por ejemplo, podrías usarlo para añadir metadatos para una interfaz de usuario frontend, etc.

///

/// info | Información

Também vimos que o HTTPS normalmente é fornecido por um componente **externo** ao seu servidor de aplicativos, um **Proxy de terminação TLS**.

E tem que haver algo responsável por **renovar os certificados HTTPS**, pode ser o mesmo componente ou pode ser algo diferente.

### Ferramentas de exemplo para HTTPS

Algumas das ferramentas que você pode usar como um proxy de terminação TLS são:

* Traefik
    * Lida automaticamente com renovações de certificados ✨