summary refs log tree commit diff
path: root/docs/CAPTCHA_SETUP.rst
diff options
context:
space:
mode:
authorDavid Baker <dave@matrix.org>2017-03-01 17:20:37 +0000
committerDavid Baker <dave@matrix.org>2017-03-01 17:20:37 +0000
commit3557cf34dc011211db1b80016ce09ada86b41ffc (patch)
tree9ff6c82f81d7a932ffc1d66d677a5cfa65157494 /docs/CAPTCHA_SETUP.rst
parentWIP support for msisdn 3pid proxy methods (diff)
parentkick jenkins (diff)
downloadsynapse-3557cf34dc011211db1b80016ce09ada86b41ffc.tar.xz
Merge remote-tracking branch 'origin/develop' into dbkr/msisdn_signin
Diffstat (limited to 'docs/CAPTCHA_SETUP.rst')
-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.