mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-02 17:59:36 +07:00
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
This commit is contained in:
committed by
backportbot[bot]
parent
c79467b0d3
commit
16f8d0c8c0
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user