From 16f8d0c8c0a68074167ec9cff8fefe2c3aa2cff3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Duveau?= Date: Thu, 2 Apr 2020 12:44:13 +0200 Subject: [PATCH] Update documentation and readability As my reverse proxy can change its IP address (self-healing, rolling update, etc) I resolve it only using internal DNS. I just tried and my Nextcloud install (officiel docker, no modifications) is able to resolve it. Options for the array have been updated for readability --- .../configuration_server/reverse_proxy_configuration.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/admin_manual/configuration_server/reverse_proxy_configuration.rst b/admin_manual/configuration_server/reverse_proxy_configuration.rst index b9bc4704c..016bfee5a 100644 --- a/admin_manual/configuration_server/reverse_proxy_configuration.rst +++ b/admin_manual/configuration_server/reverse_proxy_configuration.rst @@ -16,8 +16,12 @@ trust. Connections from trusted proxies will be specially treated to get the real client information, for use in access control and logging. Parameters are configured in :file:`config/config.php` -Set the **trusted_proxies** parameter as an array of IPv4 addresses, -IPv4 ranges in CIDR notation or IPv6 addresses to define the +Set the :file:`trusted_proxies` parameter as an array of: +* IPv4 addresses, +* IPv4 ranges in CIDR notation +* IPv6 addresses +* host to resolve +to define the servers Nextcloud should trust as proxies. This parameter provides protection against client spoofing, and you should secure those servers as you would your Nextcloud server.