Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Clarifications to reverse_proxy.md #10708

Merged
merged 2 commits into from
Aug 27, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/10708.doc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Minor clarifications to the documentation for reverse proxies.
10 changes: 5 additions & 5 deletions docs/reverse_proxy.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,9 @@ server {
server_name matrix.example.com;

location ~* ^(\/_matrix|\/_synapse\/client) {
# note: do not add a path (even a single /) after the port in `proxy_pass`,
# otherwise nginx will canonicalise the URI and cause signature verification
# errors.
proxy_pass http://localhost:8008;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
Expand All @@ -76,10 +79,7 @@ server {
}
```

**NOTE**: Do not add a path after the port in `proxy_pass`, otherwise nginx will
canonicalise/normalise the URI.

### Caddy 1
### Caddy v1

```
matrix.example.com {
Expand All @@ -99,7 +99,7 @@ example.com:8448 {
}
```

### Caddy 2
### Caddy v2
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

somebody thought these were two different interchangable examples for caddy.


```
matrix.example.com {
Expand Down