I have a problem with sending data to the client by webflux. When there is no content in Flux for about 60 seconds, response is aborted by server. Is there any possibility to "wait" for response as long as client want to?
Asked
Active
Viewed 177 times
2 Answers
0
Try this it might be helpful
.responseTimeout(Duration.ofSeconds(10))
.option(ChannelOption.CONNECT_TIMEOUT_MILLIS, 10 * 1000)
you can also refer this: Webflux Webclient - increase my Webclient time out (wait a bi more a flaky service)

Janil101
- 306
- 6
-
the problem is on the server side, because server abort connection, not client – Drake Oct 12 '22 at 10:37
0
Problem solved: Kubernetes has default value of 60 seconds for every request, so every time (for webflux) when there is no content, then reuqest is aborted (for me with status 200)

Drake
- 78
- 6