From d6053287e993a8c660613dc24096f57b9629abc2 Mon Sep 17 00:00:00 2001 From: Josh Moore Date: Sun, 25 Jul 2021 21:28:22 -0600 Subject: [PATCH] Added header for "Reverse proxies" section (#18614) Having a dedicated header for information on reverse proxies will aid users who may have missed the breaking change in 2021.7 (see https://github.com/home-assistant/core/pull/51839). I also put mimicked the `trusted_proxies` list from the sample config for clarity, and left comments for users who may still be unsure. --- source/_integrations/http.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/_integrations/http.markdown b/source/_integrations/http.markdown index 8c09417060d..2578418472a 100644 --- a/source/_integrations/http.markdown +++ b/source/_integrations/http.markdown @@ -105,13 +105,16 @@ http: The [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post gives you details about the encryption of your traffic using free certificates from [Let's Encrypt](https://letsencrypt.org/). +## Reverse proxies + When using a reverse proxy, you will need to enable the `use_x_forwarded_for` and `trusted_proxies` options. Requests from reverse proxies will be blocked if these options are not set. ```yaml http: use_x_forwarded_for: true trusted_proxies: - - 172.30.33.0/24 # Add the IP address of the proxy server + - 10.0.0.200 # Add the IP address of the proxy server + - 172.30.33.0/24 # You may also provide the subnet mask ``` ## APIs