-
Notifications
You must be signed in to change notification settings - Fork 37.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP interface client should not set a default blockingTimeout value and instead let the underlying HTTP client determine the behavior #30248
Comments
I found that it is not related to WebClient, but HttpServiceProxyFactory itself where you can need set the
This should be mentioned in the documentation as this is a bit tricky. |
Hello, @pmverma, thanks for reporting this. Although the blocking timeout settings were set there on purpose, we realise it might be more useful and intuitive to have any timeouts being governed by the underlying HTTP clients' settings. We are going to modify it so that the |
Closing as superseded by #30403. |
Affects: Spring Boot 3.0.5 / Spring Framework 6.0.7
As mentioned in the title, it seems the webclient timeout value does not work when using the HTTP interface.
But the same timeout value works when using the webclient directly as below.
I have added a minimal sample application that demonstrates the above issue.
https://github.com/pmverma/demo-http-interface-webclient-timeout
All codes are in a single file DemoHttpInterfaceWebclientTimeoutApplication.java
Regards,
Mohan
The text was updated successfully, but these errors were encountered: