mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-12-19 01:21:09 +03:00
Code Issues Projects Releases Packages Wiki Activity

Update docs/federate.md

Browse source 
Co-Authored-By: Brendan Abolivier <github@brendanabolivier.com>
This commit is contained in:
Neil Johnson 2019-06-11 11:12:07 +01:00 committed by GitHub
parent a4a9db3f88
commit ba5422601b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/federate.md
View file

@ -155,7 +155,7 @@ Practically speaking, this is no longer necessary.
If you are using a reverse proxy for all of your TLS traffic, then you can set If you are using a reverse proxy for all of your TLS traffic, then you can set
`no_tls: True`. In that case, the only reason Synapse needs the certificate is `no_tls: True`. In that case, the only reason Synapse needs the certificate is
to populate a legacy 'tls_fingerprints' field in the federation API. This is to populate a legacy `tls_fingerprints` field in the federation API. This is
ignored by Synapse 0.99.0 and later, and the only time pre-0.99 Synapses will ignored by Synapse 0.99.0 and later, and the only time pre-0.99 Synapses will
check it is when attempting to fetch the server keys - and generally this is check it is when attempting to fetch the server keys - and generally this is
delegated via `matrix.org`, which is on 0.99.0. delegated via `matrix.org`, which is on 0.99.0.