spring-projects / spring-projects/spring-boot

Investigate applying ReactorNettyHttpClientMapper beans to the HttpClient used by an auto-configured ReactorClientHttpRequestFactoryBuilder

Open
#43,365 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: pending-design-work type: enhancement
Dominant language
Java
Stars
81.5k
Forks
42.7k
Avg merge
2d 4h
Merged PRs (30d)
65

Description

I'm trying out the new HTTP client enhancements made with 3.4.0 and noticed:

  • spring.http.client properties don't apply to auto-configured WebClient.Builder instances.
  • My ReactorNettyHttpClientMapper beans are not applied to the HttpClient created by ReactorClientHttpRequestFactoryBuilder.

I was hoping to be able to simplify my configuration by re-using the same (or rather identically configured) Reactor HttpClient instances across my WebClient and RestTemplate beans, but it looks like I still need to configure those separatedly.

Are there plans to harmonize the configuration to allow the new properties and existing customizers like ReactorNettyHttpClientMapper to apply globally to all auto-configured HTTP clients?

Related:

  • #43068 (mentions WebClient, but was closed as a duplicate).
  • #43079 (wants to use the new RequestFactoryBuilder approach for WebClient).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the auto-configured WebClient.Builder and ReactorClientHttpRequestFactoryBuilder mentioned in the issue, then compare how spring.http.client properties and ReactorNettyHttpClientMapper beans are handled. Done means establishing whether those configurations can be applied consistently to both auto-configured HTTP clients and documenting or implementing the agreed approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.