diff options
| author | Brendan Abolivier <babolivier@matrix.org> | 2020-02-18 13:53:46 +0000 |
|---|---|---|
| committer | Brendan Abolivier <babolivier@matrix.org> | 2020-02-18 13:53:58 +0000 |
| commit | e837be5b5cb43406bd124e3f27a2b7be1bd31aa8 (patch) | |
| tree | dfbbc4e97b76976853b22341530f5060d92ee06c /docs/reverse_proxy.md | |
| parent | Make federate.md more of a sumary of the steps to follow to set up replication (diff) | |
| download | synapse-e837be5b5cb43406bd124e3f27a2b7be1bd31aa8.tar.xz | |
Fix links in the reverse proxy doc
Diffstat (limited to '')
| -rw-r--r-- | docs/reverse_proxy.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/reverse_proxy.md b/docs/reverse_proxy.md index dcfc5c64aa..af6d73927a 100644 --- a/docs/reverse_proxy.md +++ b/docs/reverse_proxy.md @@ -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 same server name or port. Indeed, clients will use port 443 by default, whereas servers default to port 8448. Where these are different, we -refer to the 'client port' and the \'federation port\'. See [Setting -up federation](federate.md) for more details of the algorithm used for -federation connections. +refer to the 'client port' and the \'federation port\'. See [the Matrix +specification](https://matrix.org/docs/spec/server_server/latest#resolving-server-names) +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 `https://matrix.example.com`, and other servers to connect at |