From 55f99c0e2819afaf133c02233c8a95670a2c68ee Mon Sep 17 00:00:00 2001 From: Andrew Fitzgerald Date: Tue, 24 Apr 2018 04:11:15 -0400 Subject: [PATCH] typo (#297) --- docs/src/main/asciidoc/spring-cloud-gateway.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/spring-cloud-gateway.adoc b/docs/src/main/asciidoc/spring-cloud-gateway.adoc index 584d87932..fd12b00bd 100644 --- a/docs/src/main/asciidoc/spring-cloud-gateway.adoc +++ b/docs/src/main/asciidoc/spring-cloud-gateway.adoc @@ -254,7 +254,7 @@ Spring Cloud Gateway comes with one non-default remote address resolver which is `XForwardedRemoteAddressResolver::trustAll` returns a `RemoteAddressResolver` which always takes the first IP address found in the `X-Forwarded-For` header. This approach is vulnerable to spoofing, as a malicious client could set an initial value for the `X-Forwarded-For` which would be accepted by the resolver. -`XForwardedRemoteAddressResolver::maxTrustedIndexX` takes an index which correlates to the number of trusted infrastructure running in front of Spring Cloud Gateway. +`XForwardedRemoteAddressResolver::maxTrustedIndex` takes an index which correlates to the number of trusted infrastructure running in front of Spring Cloud Gateway. If Spring Cloud Gateway is, for example only accessible via HAProxy, then a value of 1 should be used. If two hops of trusted infrastructure are required before Spring Cloud Gateway is accessible, then a value of 2 should be used.