diff options
author | babolivier <babolivier@users.noreply.github.com> | 2022-11-21 11:41:11 +0000 |
---|---|---|
committer | babolivier <babolivier@users.noreply.github.com> | 2022-11-21 11:41:11 +0000 |
commit | d1e8666ac88ad2b732c7f6ca274d856e6c3bef86 (patch) | |
tree | 440a6966e80db14ea0bba21fc93348ec800d99a9 | |
parent | deploy: 01a052789266179c70c10ea6a6253c64fd9990d2 (diff) | |
download | synapse-d1e8666ac88ad2b732c7f6ca274d856e6c3bef86.tar.xz |
deploy: 640cb3c81c927535a18b85c49a1cc2d856d03c2e
-rw-r--r-- | develop/print.html | 2 | ||||
-rw-r--r-- | develop/usage/administration/admin_api/index.html | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/develop/print.html b/develop/print.html index a4530baa79..1ea2b12ff1 100644 --- a/develop/print.html +++ b/develop/print.html @@ -10888,7 +10888,7 @@ command. This is a script that is distributed as part of synapse. It is possibly already on your <code>$PATH</code> depending on how Synapse was installed.</p> <p>Finding your user's <code>access_token</code> is client-dependent, but will usually be shown in the client's settings.</p> <h2 id="making-an-admin-api-request"><a class="header" href="#making-an-admin-api-request">Making an Admin API request</a></h2> -<p>For security reasons, we <a href="usage/administration/admin_api/reverse_proxy.html#synapse-administration-endpoints">recommend</a> +<p>For security reasons, we <a href="usage/administration/admin_api/../../../reverse_proxy.html#synapse-administration-endpoints">recommend</a> that the Admin API (<code>/_synapse/admin/...</code>) should be hidden from public view using a reverse proxy. This means you should typically query the Admin API from a terminal on the machine which runs Synapse.</p> diff --git a/develop/usage/administration/admin_api/index.html b/develop/usage/administration/admin_api/index.html index 2b6447abc1..0d5587271d 100644 --- a/develop/usage/administration/admin_api/index.html +++ b/develop/usage/administration/admin_api/index.html @@ -159,7 +159,7 @@ command. This is a script that is distributed as part of synapse. It is possibly already on your <code>$PATH</code> depending on how Synapse was installed.</p> <p>Finding your user's <code>access_token</code> is client-dependent, but will usually be shown in the client's settings.</p> <h2 id="making-an-admin-api-request"><a class="header" href="#making-an-admin-api-request">Making an Admin API request</a></h2> -<p>For security reasons, we <a href="reverse_proxy.html#synapse-administration-endpoints">recommend</a> +<p>For security reasons, we <a href="../../../reverse_proxy.html#synapse-administration-endpoints">recommend</a> that the Admin API (<code>/_synapse/admin/...</code>) should be hidden from public view using a reverse proxy. This means you should typically query the Admin API from a terminal on the machine which runs Synapse.</p> |