diff options
| author | Ike Johnson <complaints@ikejohnson.id.au> | 2019-06-02 23:10:27 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-02 23:10:27 +0800 |
| commit | 145f57897db3df082a06a791e547332278d32bfe (patch) | |
| tree | 7f2b4710e16259dc6aa493b44d45c0bee6c05a85 | |
| parent | 0.99.5.2 (diff) | |
| download | synapse-145f57897db3df082a06a791e547332278d32bfe.tar.xz | |
Update HAProxy example rules
These new rules allow a user to instead route only matrix traffic, allowing them to run matrix on the domain without affecting their existing websites
Diffstat (limited to '')
| -rw-r--r-- | docs/reverse_proxy.rst | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/reverse_proxy.rst b/docs/reverse_proxy.rst index 7619b1097b..e4b870411c 100644 --- a/docs/reverse_proxy.rst +++ b/docs/reverse_proxy.rst @@ -89,8 +89,10 @@ Let's assume that we expect clients to connect to our server at bind :::443 v4v6 ssl crt /etc/ssl/haproxy/ strict-sni alpn h2,http/1.1 # Matrix client traffic - acl matrix hdr(host) -i matrix.example.com - use_backend matrix if matrix + acl matrix-host hdr(host) -i matrix.example.com + acl matrix-path path_beg /_matrix + + use_backend matrix if matrix-host matrix-path frontend matrix-federation bind :::8448 v4v6 ssl crt /etc/ssl/haproxy/synapse.pem alpn h2,http/1.1 |