summary refs log tree commit diff
diff options
context:
space:
mode:
authorDaniel Dent <DanielDent@users.noreply.github.com>2017-02-08 21:21:02 -0800
committerGitHub <noreply@github.com>2017-02-08 21:21:02 -0800
commitfdbd90e25dc3682c4d6aa1dd85a9e0e4fedabb1a (patch)
tree2acbed1541d8ac170e06f49649397b09786ec0bc
parentMake None check explicit (diff)
downloadsynapse-fdbd90e25dc3682c4d6aa1dd85a9e0e4fedabb1a.tar.xz
Update CAPTCHA_SETUP.rst X-Forwarded-For docs
It looks like CAPTCHA_SETUP.rst contains information relevant to an old version of Synapse, but Synapse now has a different approach to configuring use of the X-Forwarded-For header.
-rw-r--r--docs/CAPTCHA_SETUP.rst5
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/CAPTCHA_SETUP.rst b/docs/CAPTCHA_SETUP.rst
index db621aedfc..19a204d9ce 100644
--- a/docs/CAPTCHA_SETUP.rst
+++ b/docs/CAPTCHA_SETUP.rst
@@ -25,6 +25,5 @@ Configuring IP used for auth
 The ReCaptcha API requires that the IP address of the user who solved the
 captcha is sent. If the client is connecting through a proxy or load balancer,
 it may be required to use the X-Forwarded-For (XFF) header instead of the origin
-IP address. This can be configured as an option on the home server like so::
-
-  captcha_ip_origin_is_x_forwarded: true
+IP address. This can be configured using the x_forwarded directive in the
+listeners section of the homeserver.yaml configuration file.