diff options
| author | Matthew Hodgson <matthew@matrix.org> | 2019-02-05 17:02:20 +0000 |
|---|---|---|
| committer | Matthew Hodgson <matthew@matrix.org> | 2019-02-05 17:02:20 +0000 |
| commit | e12165ff2b60f567305528a251ab77d9eb617dfa (patch) | |
| tree | 885447ed00af8c490ee33256030b4c7f931a1a00 | |
| parent | MD tweaks (diff) | |
| download | synapse-e12165ff2b60f567305528a251ab77d9eb617dfa.tar.xz | |
MD tweaks
| -rw-r--r-- | docs/MSC1711_certificates_FAQ.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/MSC1711_certificates_FAQ.md b/docs/MSC1711_certificates_FAQ.md index 05b4068f79..b3726df54b 100644 --- a/docs/MSC1711_certificates_FAQ.md +++ b/docs/MSC1711_certificates_FAQ.md @@ -227,7 +227,7 @@ We no longer actively recommend against using a reverse proxy. Many admins will find it easier to direct federation traffic to a reverse-proxy and manage their own TLS certificates, and this is a supported configuration. -Do I still need to give my TLS certificates to Synapse if I am using a +### Do I still need to give my TLS certificates to Synapse if I am using a reverse-proxy? Practically speaking, this is no longer necessary. |