From 15089c5706b7aaf1b6843916653f34b6aff0025c Mon Sep 17 00:00:00 2001 From: Jun Kurihara Date: Sat, 6 Aug 2022 21:47:29 +0900 Subject: [PATCH 1/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 85faca8..2697085 100644 --- a/README.md +++ b/README.md @@ -120,7 +120,7 @@ reverse_proxy = [ ### Second Step: Terminating TLS -First of all, you need to specify a port `listen_port_tls` listening the HTTPS traffic, separately from HTTPS port (`listen_port`). Then, serving an HTTPS endpoint can be easily done for your desired application just by specifying TLS certificates and private keys in PEM files. +First of all, you need to specify a port `listen_port_tls` listening the HTTPS traffic, separately from HTTP port (`listen_port`). Then, serving an HTTPS endpoint can be easily done for your desired application just by specifying TLS certificates and private keys in PEM files. ```toml listen_port = 80 From b41f2bd35225e92b93ce727e9cbce20f510a9cc2 Mon Sep 17 00:00:00 2001 From: Jun Kurihara Date: Sat, 6 Aug 2022 21:52:26 +0900 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2697085..2d84cd5 100644 --- a/README.md +++ b/README.md @@ -232,7 +232,7 @@ Other than them, all you need is to mount your `config.toml` as `/etc/rpxy.toml` If you obtain certificates and private keys from [Let's Encrypt](https://letsencrypt.org/), you have PKCS1-formatted private keys. So you need to convert such retrieved private keys into PKCS8 format to use in `rpxy`. -The most easiest way is to use `openssl` by +The easiest way is to use `openssl` by ```bash openssl pkcs8 -topk8 -nocrypt \