From 8a5560ee83e93d67e10c73eacf2a852553c9bd5a Mon Sep 17 00:00:00 2001 From: Chris Browet Date: Mon, 12 Jul 2021 17:10:11 +0200 Subject: [PATCH] Clarifies usage of trusted_proxies (#18447) * Clarifies usage of trusted_proxies As discussed in https://github.com/home-assistant/core/issues/52736 * Tweak Co-authored-by: Franck Nijhof --- source/_integrations/http.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown index c5b9dcfd93d..8c09417060d 100644 --- a/source/_integrations/http.markdown +++ b/source/_integrations/http.markdown @@ -64,7 +64,7 @@ use_x_forwarded_for: type: boolean default: false trusted_proxies: - description: "List of trusted proxies, consisting of IP addresses or networks, that are allowed to set the `X-Forwarded-For` header. This is required when using `use_x_forwarded_for` because all requests to Home Assistant, regardless of source, will arrive from the reverse proxy IP address. Therefore in a reverse proxy scenario, this option should be set with extreme care." + description: "List of trusted proxies, consisting of IP addresses or networks, that are allowed to set the `X-Forwarded-For` header. This is required when using `use_x_forwarded_for` because all requests to Home Assistant, regardless of source, will arrive from the reverse proxy IP address. Therefore in a reverse proxy scenario, this option should be set with extreme care. If the immediate upstream proxy is not in the list, the request will be rejected. If any other intermediate proxy is not in the list, the first untrusted proxy will be considered the client." required: false type: [string, list] ip_ban_enabled: