Merge pull request #4055 from edwardando/patch-1

add 302 redirect option as well as reverse-proxy
spantaleev · Feb 11, 2025 · 427585f · 427585f
2 parents 00bde4a + 6dfe5d5
commit 427585f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md
@@ -97,7 +97,7 @@ This is relatively easy to do and possibly your only choice if you can only host
 
 This option is less fragile and generally better.
 
-On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`).
+On the base domain's server (e.g. `example.com`), you can set up reverse-proxying (or simply a 302 redirect), so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`).
 
 With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly.