Files
rikako-note/spring/webflux/webclient.md
2025-04-22 12:52:03 +08:00

4.0 KiB
Raw Blame History

WebClient

WebClient基于Reactor提供了functional, fluent API

WebClient是非阻塞的其依赖的codecs和server端使用的codecs相同。

Configuration

创建WebClient最简单的方式是通过静态工厂方法:

  • WebClient.create()
  • WebClient.create(String baseUrl)

除此之外,也可以通过WebClient.builder()来指定更多选项:

  • uriBuilderFactory 自定义uriBuilderFactory用于创建UriBuilderUriBuilder包含共享的配置例如base URI等
  • defaultUriVariables: 在拓展uri templates时使用到的默认值
  • defaultHeader对每个请求都包含的headers
  • defaultCookie每个请求都包含的Cookie
  • defaultRequest 对每个请求进行自定义的Consumer
  • filter对于每个请求的client filter
  • exchangeStrategies自定义http message的reader/writer
  • clientConnectorhttp client library设置
  • observationRegistry the registry to use for enabling Observability support
  • observationConvention: an optional, custom convention to extract metadata for recorded observations.

创建WebClient的示例如下

WebClient client = WebClient.builder()
		.codecs(configurer -> ... )
		.build();

一旦被创建后WebClient是不可变的但是,可以对其进行克隆并对副本进行修改,示例如下:

WebClient client1 = WebClient.builder()
		.filter(filterA).filter(filterB).build();

WebClient client2 = client1.mutate()
		.filter(filterC).filter(filterD).build();

// client1 has filterA, filterB

// client2 has filterA, filterB, filterC, filterD

MaxInMemorySize

Codecs对于缓存在内存中的数据大小存在限制避免导致应用的内存问题。默认情况下该值被设置为256KB,如果该大小不够,那么将会见到如下报错:

org.springframework.core.io.buffer.DataBufferLimitException: Exceeded limit on max bytes to buffer

如果想要修改该默认的codecs限制可以使用如下配置

WebClient webClient = WebClient.builder()
		.codecs(configurer -> configurer.defaultCodecs().maxInMemorySize(2 * 1024 * 1024))
		.build();

reactor netty

为了自定义reactor netty配置可以提供一个预先定义的HttpClient

HttpClient httpClient = HttpClient.create().secure(sslSpec -> ...);

WebClient webClient = WebClient.builder()
		.clientConnector(new ReactorClientHttpConnector(httpClient))
		.build();

Resources

默认情况下,HttpClient将会参与使用reactor.netty.http.HttpResources中保存的全局reactor netty resources。

HttpResources中包含event loop threads和connection poolHttpClient会使用这些共享的资源。对于基于event loop的并发更倾向使用固定、共享的资源直到进程退出时这些全局资源才会被释放。

如果server的生命周期和进程相同那么对全局资源无需手动释放。但若server在进程的生命周期中可能会启动和停止那么可以声明一个ReactorResourceFactory类型的bean并设置globalResources=true默认从而确保reactor netty的global resource在ApplicationContext关闭时被释放,示例如下所示:

@Bean
public ReactorResourceFactory reactorResourceFactory() {
	return new ReactorResourceFactory();
}

也可以不使用global reactor netty resources但是在该模式下你需要确保所有reactor netty client and server使用共享的资源示例如下所示

@Bean
public ReactorResourceFactory resourceFactory() {
	ReactorResourceFactory factory = new ReactorResourceFactory();
	factory.setUseGlobalResources(false); 
	return factory;
}

@Bean
public WebClient webClient() {

	Function<HttpClient, HttpClient> mapper = client -> {
		// Further customizations...
	};

	ClientHttpConnector connector =
			new ReactorClientHttpConnector(resourceFactory(), mapper); 

	return WebClient.builder().clientConnector(connector).build(); 
}