clarifying reverse proxying of well-known files

This commit is contained in:
Arkonos 2022-05-08 21:20:36 +02:00
parent 25302ed142
commit 6abdb6e6f0
2 changed files with 33 additions and 2 deletions

View File

@ -116,8 +116,22 @@ server {
**For Caddy 2**, it would be something like this: **For Caddy 2**, it would be something like this:
```caddy ```caddy
reverse_proxy /.well-known/matrix/* https://matrix.DOMAIN { DOMAIN.com {
header_up Host {http.reverse_proxy.upstream.hostport} @wellknown {
path /.well-known/matrix/*:x
}
handle @wellknown {
reverse_proxy https://matrix.DOMAIN.com {
header_up Host {http.reverse_proxy.upstream.hostport}
}
}
# Configration for the base domain goes here
# handle {
# header -Server
# encode zstd gzip
# reverse_proxy localhost:4020
# }
} }
``` ```

View File

@ -214,3 +214,20 @@ element.DOMAIN.tld {
# } # }
# } # }
#} #}
DOMAIN.com {
@wellknown {
path /.well-known/matrix/*
}
handle @wellknown {
reverse_proxy https://matrix.DOMAIN.com {
header_up Host {http.reverse_proxy.upstream.hostport}
}
}
# Configration for the base domain goes here
# handle {
# header -Server
# encode zstd gzip
# reverse_proxy localhost:4020
# }
}