When using the Reactive Streams API to consume long running chunked HTTP responses, read timeouts occur on active connections that are actually receiving data constantly from the server. The only way to use Reactive Streams with AHC in this manner is to disable read timeouts.
It seems that NettyResponseFuture.touch() isn't called when passing HttpResponseBodyPart instances to the StreamedResponsePublisher in AsyncHttpClientHandler.
Is that intended behavior, or something that has just been overlooked?
In the latter case, what would be the right place to touch the future then? Somewhere below here maybe?
When using the Reactive Streams API to consume long running chunked HTTP responses, read timeouts occur on active connections that are actually receiving data constantly from the server. The only way to use Reactive Streams with AHC in this manner is to disable read timeouts.
It seems that
NettyResponseFuture.touch()isn't called when passingHttpResponseBodyPartinstances to theStreamedResponsePublisherinAsyncHttpClientHandler.Is that intended behavior, or something that has just been overlooked?
In the latter case, what would be the right place to
touchthe future then? Somewhere below here maybe?