Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`WebClient` with default codecs drops `ProblemDetail` extension members

Open Beginner friendly
  • Is something wrong?
#37,503 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #37507 by @zsewasdsdsd — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java, spring
Domain
backend

Research direction

The gap is in JacksonJsonDecoder under org.springframework.http.codec.json, which unlike JacksonJsonEncoder never registers ProblemDetailJacksonMixin in its default and JsonMapper.Builder constructors. Start by comparing those two classes side by side, then look at the existing codec tests for ProblemDetail decoding to see where a mirror test for the decoder belongs. Done means a WebClient built with default codecs keeps extension members in getProperties(), reproduced with the sample at noojung/webclient-problemdetail-mixin-repro. Note that a PR (#37507) was already opened and closed unmerged, so check the thread before duplicating it.

Written by the indexing model from the issue text.

Description

status: waiting-for-triage

Overview

While checking that RestClient and WebClient decode ProblemDetail responses correctly, I noticed that a WebClient created with the default codecs (WebClient.create() or WebClient.builder()) drops RFC 9457 extension members: getProperties() returns null, while the standard members are decoded correctly.

This worked with Spring Framework 6.2 (Spring Boot 3.5), so it looks like a regression introduced with the Jackson 3 codecs.

Versions tested

  • Spring Framework 7.0.9 (Spring Boot 4.1.1, Jackson 3): extension members are lost
  • Spring Framework 6.2.11 (Spring Boot 3.5.6, Jackson 2): works as expected

Reproducer

With the sample server running on port 8080, GET /orders/42 returns HTTP 404 with Content-Type: application/problem+json and the following body:

{
  "type": "https://example.com/problems/order-not-found",
  "title": "Order Not Found",
  "status": 404,
  "detail": "Order 42 does not exist",
  "instance": "/orders/42",
  "errorCode": "ORDER_NOT_FOUND",
  "orderId": 42
}

The extension members are lost when decoding the response:

WebClient webClient = WebClient.create("http://localhost:8080");
// Also reproduces with:
// WebClient.builder().baseUrl("http://localhost:8080").build();

WebClientResponseException.NotFound exception = assertThrows(
        WebClientResponseException.NotFound.class,
        () -> webClient.get()
                .uri("/orders/42")
                .retrieve()
                .bodyToMono(Order.class)
                .block());

ProblemDetail problemDetail = exception.getResponseBodyAs(ProblemDetail.class);

assertThat(problemDetail).isNotNull();
assertThat(problemDetail.getProperties())
        .containsEntry("errorCode", "ORDER_NOT_FOUND")
        .containsEntry("orderId", 42);
// 6.2.11: passes
// 7.0.9:  fails because getProperties() returns null

A complete sample (Spring MVC server + WebClient/RestClient tests) is available here: https://github.com/noojung/webclient-problemdetail-mixin-repro

Running ./gradlew test starts the server automatically and fails webClientCreateShouldPreserveProblemDetailProperties and webClientBuilderShouldPreserveProblemDetailProperties.

For comparison, RestClient.create() and the WebClient.Builder auto-configured by Spring Boot both keep the extension members, since JacksonJsonHttpMessageConverter registers the mixin and Boot configures the codecs with a JsonMapper that has it (spring-projects/spring-boot#47298).

Analysis

JacksonJsonEncoder and JacksonJsonHttpMessageConverter register ProblemDetailJacksonMixin in their default and JsonMapper.Builder-based constructors, but JacksonJsonDecoder does not. Since FAIL_ON_UNKNOWN_PROPERTIES is disabled by default in Jackson 3, the extension members are ignored without any error.

With Jackson 2, the default Jackson2JsonDecoder created its mapper through Jackson2ObjectMapperBuilder, which registers the mixin.

Workaround

WebClient webClient = WebClient.builder()
        .codecs(configurer -> configurer.defaultCodecs().jacksonJsonDecoder(new JacksonJsonDecoder(
                JsonMapper.builder().addMixIn(ProblemDetail.class, ProblemDetailJacksonMixin.class))))
        .build();

Related issues

  • #35597
  • spring-projects/spring-boot#47298

Would registering ProblemDetailJacksonMixin in the default and JsonMapper.Builder-based constructors of JacksonJsonDecoder, the same way as in JacksonJsonEncoder, be the right fix? If so, I would be happy to submit a pull request.

Dominant language
Java
Stars
60.3k
Forks
38.7k
Avg merge
1d 13h
Merged PRs (30d)
36

Getting set up

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.

More from spring-projects/spring-framework

All issues in spring-projects/spring-framework

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.