In particular:
- add missing `new` operator
- ensure that `RouteDefinitionLocators` is properly formatted in the "Configuration" section
- "Normwal" -> "Normal"
- remove extra "`"
@ -1226,7 +1226,7 @@ As Spring Cloud Gateway distinguishes between "pre" and "post" phases for filter
@@ -1226,7 +1226,7 @@ As Spring Cloud Gateway distinguishes between "pre" and "post" phases for filter
----
@Bean
public GlobalFilter customFilter() {
return CustomGlobalFilter();
return new CustomGlobalFilter();
}
public class CustomGlobalFilter implements GlobalFilter, Ordered {
@ -1324,7 +1324,7 @@ The `NettyWriteResponseFilter` runs if there is a Netty `HttpClientResponse` in
@@ -1324,7 +1324,7 @@ The `NettyWriteResponseFilter` runs if there is a Netty `HttpClientResponse` in
=== RouteToRequestUrl Filter
The `RouteToRequestUrlFilter` runs if there is a `Route` object in the `ServerWebExchangeUtils.GATEWAY_ROUTE_ATTR` exchange attribute. It creates a new URI, based off of the request URI, but updated with the URI attribute of the `Route` object. The new URI is placed in the `ServerWebExchangeUtils.GATEWAY_REQUEST_URL_ATTR` exchange attribute`.
The `RouteToRequestUrlFilter` runs if there is a `Route` object in the `ServerWebExchangeUtils.GATEWAY_ROUTE_ATTR` exchange attribute. It creates a new URI, based off of the request URI, but updated with the URI attribute of the `Route` object. The new URI is placed in the `ServerWebExchangeUtils.GATEWAY_REQUEST_URL_ATTR` exchange attribute.
If the URI has a scheme prefix, such as `lb:ws://serviceid`, the `lb` scheme is stripped from the URI and placed in the `ServerWebExchangeUtils.GATEWAY_SCHEME_PREFIX_ATTR` for use later in the filter chain.