Make sure use_x_forward_for and trusted_proxies must config together

[awarecan]

Description:

Per http component document and PR #15204

use_x_forwarded_for (Optional): Enable parsing of the X-Forwarded-For header, passing on the client’s correct IP address in proxied setups. You must also whitelist trusted proxies using the trusted_proxies setting below for this to work.

However, we don't have config validation against this requirement.

This PR added config validation to make sure these two options are configured together

Related issue (if applicable): fixes #15544

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[houndci-bot]

blank line at end of file

[houndci-bot]

continuation line missing indentation or outdented

[houndci-bot]

continuation line missing indentation or outdented

[awarecan]

I don't have proxy server setup, need volunteer to test it.

cc @andersonshatch @mvn23

[brunohorta82]

Hello in my case not show the real IP only de proxy IP

http: api_password: !secret api_password server_port: !secret api_port base_url: https://home.bhsystems.eu use_x_forwarded_for: true trusted_proxies: 127.0.0.1 ip_ban_enabled: true login_attempts_threshold: 5

Nginx

proxy_set_header Host $host; proxy_redirect http:// https://; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; }

[awarecan]

@brunohorta82 please do not use pull request to raise issue, create an issue and fill in the issue template.