gateway 过滤器执行顺序_Spring Cloud Gateway 默认的filter功能和执行顺序

本文详细介绍了Spring Cloud Gateway的过滤器执行顺序,从AdaptCachedBodyGlobalFilter到ForwardRoutingFilter,包括替换请求体、响应处理、路径替换、负载均衡、WebSocket代理等功能。通过GlobalFilter调试方法,可以查看并理解每个过滤器的作用。
摘要由CSDN通过智能技术生成

有效性

Spring Cloud Gateway 2.0.0.RELEASE

调试方法

新建一个GlobalFilter,在filter中加断点即可调试filter,通过chain参数可以查看其它的filter及执行顺序(order)

filters(按执行顺序)

1. AdaptCachedBodyGlobalFilter

核心代码

public int getOrder() {

return Ordered.HIGHEST_PRECEDENCE + 1000;

}

public static final String CACHED_REQUEST_BODY_KEY = "cachedRequestBody";

public Mono filter(ServerWebExchange exchange, GatewayFilterChain chain) {

Flux body = exchange.getAttributeOrDefault(CACHED_REQUEST_BODY_KEY, null);

if (body != null) {

ServerHttpRequestDecorator decorator = new ServerHttpRequestDecorator(exchange.getRequest()) {

@Override

public Flux getBody() {

return body;

}

};

return chain.filter(exchange.mutate().request(decorator).build());

}

return chain.filter(exchange);

}

提供替换request 的 body的能力

2.NettyWriteResponseFilter

核心代码

public static final int WRITE_RESPONSE_FILTER_ORDER = -1;

public int getOrder() {

return WRITE_RESPONSE_FILTER_ORDER;

}

public Mono filter(ServerWebExchange exchange, GatewayFilterChain chain) {

return chain.filter(exchange).then(Mono.defer(() -> {

//见 后文的 NettyRoutingFilter

HttpClientResponse clientResponse = exchange.getAttribute(CLIENT_RESPONSE_ATTR);

ServerHttpResponse response = exchange.getResponse();

NettyDataBufferFactory factory = (NettyDataBufferFactory) response.bufferFactory();

final Flux body = clientResponse.receive()

.map(factory::wrap);

MediaType contentType = response.getHeaders().getContentType();

return (isStreamingMediaType(contentType) ?

response.writeAndFlushWith(body.map(Flux::just)) : response.writeWi

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值