RestClient requestInterceptor not invoked after Spring Boot upgrade.

[rpapeters]

Since upgrading Spring Boot from 3.3.x to 3.4.x (spring-web from 6.1.x to 6.2.x) any registered request interceptors are not invoked.

For example we have this RestClient:

        final var restClient = RestClient.builder()
                .baseUrl(integralityUrl + "/api")
                .requestInterceptor((HttpRequest request, byte[] body, ClientHttpRequestExecution execution) -> {
                    System.out.println("THIS WILL NOT BE EXECUTED");
                    return execution.execute(request, body);
                })
                .build();

        restClient.get().uri("/some-endpoint").retrieve();

In this example the requestInterceptor is never invoked.

When looking into the code of spring-web 6.1.18 and 6.2.0 there is a difference in the retrieve function:

6.1.18

        public RestClient.ResponseSpec retrieve() {
            RestClient.ResponseSpec responseSpec = (RestClient.ResponseSpec)this.exchangeInternal((x$0, x$1) -> {
                return DefaultRestClient.this.new DefaultResponseSpec(x$0, x$1);
            }, false);
            Assert.state(responseSpec != null, "No ResponseSpec");
            return responseSpec;
        }

this.exchangeInternal will invoke createRequest which will invoke the interceptors.

6.2.0

        public RestClient.ResponseSpec retrieve() {
            return DefaultRestClient.this.new DefaultResponseSpec(this);
        }

this.exchangeInternal is not invoked.

Is this a bug or should it be configured differently?

[sbrannen]

Hi @rpapeters,

Congratulations on submitting your first issue for the Spring Framework! 👍

Is this a bug or should it be configured differently?

This change in behavior is to be expected.

See:

• Update retrieve() in RestClient to execute and extract in single scope  #33777
• Introduce @CheckReturnValue annotation #33818

As documented in the HTTP clients section of the 6.2 release notes, you'll need to invoke a terminal operation on the ResponseSpec.

For example:

restClient.get().uri("/some-endpoint").retrieve().toBodilessEntity();

In light of the above, I am closing this issue.

[taarh]

Hello @rpapeters

HTTP Clients
The behavior of the RestClient API has been updated to ensure consistency with other HTTP clients and to resolve issues related to observability. Previously, invoking:

ResponseSpec spec = restClient.get().uri("/spring").retrieve();
would immediately trigger the request in a "fire-and-forget" manner, often leaving observation scopes incomplete.

Starting from version 6.2, this line of code no longer has any effect unless a terminal operation is explicitly called on the ResponseSpec. To execute the request and trigger side effects, developers must now use a terminal method, such as:

ResponseEntity<Void> response = restClient.get().uri("/spring").retrieve().toBodilessEntity();

Doc
https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-6.2-Release-Notes#http-clients

[rpapeters]

Ah, it’s also in the docs as a note. Should have seen that, sorry and thx for the quick reply 😄 Op 11 apr 2025 om 16:40 heeft Sam Brannen ***@***.***> het volgende geschreven:  Hi @rpapeters<https://github.com/rpapeters>, Congratulations on submitting your first issue for the Spring Framework! 👍 Is this a bug or should it be configured differently? This change in behavior is to be expected. See: * #33777<#33777> * #33818<#33818> As documented in the HTTP clients<https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-6.2-Release-Notes#http-clients> section of the 6.2 release notes, you'll need to invoke a terminal operation on the ResponseSpec. For example: restClient.get().uri("/some-endpoint").retrieve().toBodilessEntity(); In light of the above, I am closing this issue. — Reply to this email directly, view it on GitHub<#34743 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAXXJ6VHXLNEW3NMTCOAK432Y7H47AVCNFSM6AAAAAB26J7GYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJXGEYTENJYG4>. You are receiving this because you were mentioned.Message ID: ***@***.***> [https://avatars.githubusercontent.com/u/104798?s=20&v=4]sbrannen left a comment (spring-projects/spring-framework#34743)<#34743 (comment)> Hi @rpapeters<https://github.com/rpapeters>, Congratulations on submitting your first issue for the Spring Framework! 👍 Is this a bug or should it be configured differently? This change in behavior is to be expected. See: * #33777<#33777> * #33818<#33818> As documented in the HTTP clients<https://github.com/spring-projects/spring-framework/wiki/Spring-Framework-6.2-Release-Notes#http-clients> section of the 6.2 release notes, you'll need to invoke a terminal operation on the ResponseSpec. For example: restClient.get().uri("/some-endpoint").retrieve().toBodilessEntity(); In light of the above, I am closing this issue. — Reply to this email directly, view it on GitHub<#34743 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAXXJ6VHXLNEW3NMTCOAK432Y7H47AVCNFSM6AAAAAB26J7GYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJXGEYTENJYG4>. You are receiving this because you were mentioned.Message ID: ***@***.***>