diff --git a/spring-cloud-gateway.html b/spring-cloud-gateway.html index 98c4d8ff..d9034890 100644 --- a/spring-cloud-gateway.html +++ b/spring-cloud-gateway.html @@ -393,7 +393,7 @@ URIs defined in routes without a port will get a default port set to 80 and 443
-

This route matches if the request has a header named X-Request-Id whos value matches the \d+ regular expression (has a value of one or more digits).

+

This route matches if the request has a header named X-Request-Id whose value matches the \d+ regular expression (has a value of one or more digits).

@@ -449,7 +449,7 @@ URIs defined in routes without a port will get a default port set to 80 and 443

Path Route Predicate Factory

-

The Path Route Predicate Factory takes two parameter: a list of Spring PathMatcher patterns and an optional flag to matchOptionalTrailingSeparator.

+

The Path Route Predicate Factory takes two parameters: a list of Spring PathMatcher patterns and an optional flag to matchOptionalTrailingSeparator.

application.yml
@@ -847,7 +847,7 @@ a fallbackUri in an external application, like in the following sce
-

In this example, after an execution exception occurs while running the HystrixCommand, the request will be forwarde to +

In this example, after an execution exception occurs while running the HystrixCommand, the request will be forwarded to the fallback endpoint or handler in an app running on localhost:9994. The headers with the exception type, message and -if available- root cause exception type and message will be added to that request by the FallbackHeaders filter.

@@ -900,7 +900,7 @@ their default values:

PreserveHostHeader GatewayFilter Factory

-

The PreserveHostHeader GatewayFilter Factory has not parameters. This filter, sets a request attribute that the routing filter will inspect to determine if the original host header should be sent, rather than the host header determined by the http client.

+

The PreserveHostHeader GatewayFilter Factory has no parameters. This filter sets a request attribute that the routing filter will inspect to determine if the original host header should be sent, rather than the host header determined by the http client.

application.yml
@@ -942,7 +942,7 @@ their default values:

The default implementation of KeyResolver is the PrincipalNameKeyResolver which retrieves the Principal from the ServerWebExchange and calls Principal.getName().

-

By default, if the KeyResolver does not find a key, requests will be denied. This behavior can be adjust with the spring.cloud.gateway.filter.request-rate-limiter.deny-empty-key (true or false) and spring.cloud.gateway.filter.request-rate-limiter.empty-key-status-code properties.

+

By default, if the KeyResolver does not find a key, requests will be denied. This behavior can be adjusted with the spring.cloud.gateway.filter.request-rate-limiter.deny-empty-key (true or false) and spring.cloud.gateway.filter.request-rate-limiter.empty-key-status-code properties.

@@ -1215,7 +1215,7 @@ using something like Spring

The SecureHeaders GatewayFilter Factory adds a number of headers to the response at the reccomendation from this blog post.

-
The following headers are added (allong with default values):
+
The following headers are added (along with default values):

  • X-Xss-Protection:1; mode=block

    @@ -1351,7 +1351,7 @@ using something like Spring

    StripPrefix GatewayFilter Factory

    -

    The StripPrefix GatewayFilter Factory takes one paramter, parts. The parts parameter indicated the number of parts in the path to strip from the request before sending it downstream.

    +

    The StripPrefix GatewayFilter Factory takes one parameter, parts. The parts parameter indicated the number of parts in the path to strip from the request before sending it downstream.

    application.yml
    @@ -1842,7 +1842,7 @@ or check if an exchange has already been routed.

    -

    Using an insecure trust manager is not suitable for production. For a production deployment the Gateway can be configured with a set of known certificates that it can trust with the follwing configuration:

    +

    Using an insecure trust manager is not suitable for production. For a production deployment the Gateway can be configured with a set of known certificates that it can trust with the following configuration:

    application.yml
    @@ -1858,12 +1858,12 @@ or check if an exchange has already been routed.

-

If the Spring Cloud Gateway is not provisioned with trusted certificates the default trust store is used (which can be overriden with system property javax.net.ssl.trustStore).

+

If the Spring Cloud Gateway is not provisioned with trusted certificates the default trust store is used (which can be overridden with system property javax.net.ssl.trustStore).

TLS Handshake

-

The Gateway maintains a client pool that it uses to route to backends. When communicating over https the client initiates a TLS handshake. A number of timeouts are assoicated with this handshake. These timeouts can be configured (defaults shown):

+

The Gateway maintains a client pool that it uses to route to backends. When communicating over https the client initiates a TLS handshake. A number of timeouts are associated with this handshake. These timeouts can be configured (defaults shown):

application.yml