tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity

Fix links in the reverse proxy doc

Browse source
This commit is contained in:
Brendan Abolivier 2020-02-18 13:53:46 +00:00
parent 3c67eee6dc
commit e837be5b5c
No known key found for this signature in database
GPG key ID: 1E015C145F1916CD
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/reverse_proxy.md
View file

@ -18,9 +18,10 @@ When setting up a reverse proxy, remember that Matrix clients and other
Matrix servers do not necessarily need to connect to your server via the Matrix servers do not necessarily need to connect to your server via the
same server name or port. Indeed, clients will use port 443 by default, same server name or port. Indeed, clients will use port 443 by default,
whereas servers default to port 8448. Where these are different, we whereas servers default to port 8448. Where these are different, we
refer to the 'client port' and the \'federation port\'. See [Setting refer to the 'client port' and the \'federation port\'. See [the Matrix
up federation](federate.md) for more details of the algorithm used for specification](https://matrix.org/docs/spec/server_server/latest#resolving-server-names)
federation connections. for more details of the algorithm used for federation connections, and
[delegate.md](<delegate.md>) for instructions on setting up delegation.
Let's assume that we expect clients to connect to our server at Let's assume that we expect clients to connect to our server at
`https://matrix.example.com`, and other servers to connect at `https://matrix.example.com`, and other servers to connect at