mirror of
https://github.com/caddyserver/website.git
synced 2025-04-22 04:56:17 -04:00
Update src/docs/markdown/caddyfile/options.md
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
This commit is contained in:
parent
ea612a9878
commit
2f1e957d69
1 changed files with 1 additions and 1 deletions
|
@ -853,7 +853,7 @@ Here's a complete example, trusting an example IPv4 range and an IPv6 range:
|
||||||
|
|
||||||
##### `trusted_proxies_strict`
|
##### `trusted_proxies_strict`
|
||||||
|
|
||||||
When [`trusted_proxies`](#trusted-proxies) is enabled, the [`client_ip_headers`](#client-ip-headers) are parsed from left-to-right by default. The first untrusted IP address found becomes the real client address. Since v2.8, you can opt-in to right-to-left parsing of these headers with `trusted_proxies_strict`. By default, this option is disabled for backwards compatibility.
|
When [`trusted_proxies`](#trusted-proxies) is enabled, the IPs in the headers (configured by [`client_ip_headers`](#client-ip-headers)) are parsed from left-to-right by default. The first untrusted IP address found becomes the real client address. Since v2.8, you can opt-in to right-to-left parsing of these headers with `trusted_proxies_strict`. By default, this option is disabled for backwards compatibility.
|
||||||
|
|
||||||
Upstream proxies such as HAProxy, CloudFlare, AWS ALB, CloudFront, etc. will append each new connecting remote address to the right of `X-Forwarded-For`. It is recommended to enable `trusted_proxies_strict` when working with these, as the left-most IP address may be spoofed by the client.
|
Upstream proxies such as HAProxy, CloudFlare, AWS ALB, CloudFront, etc. will append each new connecting remote address to the right of `X-Forwarded-For`. It is recommended to enable `trusted_proxies_strict` when working with these, as the left-most IP address may be spoofed by the client.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue