[
https://issues.apache.org/jira/browse/HTTPCLIENT-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Kumar updated HTTPCLIENT-2169:
--------------------------------------
Description:
h4. Description
The httpclient (both sync and sync) supports `connectTimeout`,
`responseTimeout` and `connectionRequestTimeout`. But it doesn't support
complete request or call timeout similar to okhttp `callTimeout` :
[https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/call-timeout/].
Based on my understanding the `responseTimeout` is nothing but `readTimeout`
i.e. the maximum time the client will wait for a message to arrive and
theoretically, the total call time can be infinite if the server keeps sending
msg within specified `readTimeout`. It can be problematic if the client wants
to put a hard limit on the complete call time. I believe it's a very common use
case in a low latency system.
*Proposed Solution*
Provide option to user to specify `callTimeout`/`requestTimeout`
was:
h4. Description
The httpclient (both sync and sync) supports `connectTimeout`,
`responseTimeout` and `connectionRequestTimeout`. But it doesn't support
complete request or call timeout similar to okhttp `callTimeout`
([link|[https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/call-timeout/]).]
Based on my understanding the `responseTimeout` is nothing but `readTimeout`
i.e. the maximum time the client will wait for a message to arrive and
theoretically, the total call time can be infinite if the server keeps sending
msg within specified `readTimeout`. It can be problematic if the client wants
to put a hard limit on the complete call time. I believe it's a very common use
case in a low latency system.
*Proposed Solution*
Provide option to user to specify `callTimeout`/`requestTimeout`
> Support to provide complete request/call timeout option
> -------------------------------------------------------
>
> Key: HTTPCLIENT-2169
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2169
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (async), HttpClient (classic)
> Affects Versions: 5.1
> Reporter: Nishant Kumar
> Priority: Major
>
> h4. Description
> The httpclient (both sync and sync) supports `connectTimeout`,
> `responseTimeout` and `connectionRequestTimeout`. But it doesn't support
> complete request or call timeout similar to okhttp `callTimeout` :
> [https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/call-timeout/].
> Based on my understanding the `responseTimeout` is nothing but `readTimeout`
> i.e. the maximum time the client will wait for a message to arrive and
> theoretically, the total call time can be infinite if the server keeps
> sending msg within specified `readTimeout`. It can be problematic if the
> client wants to put a hard limit on the complete call time. I believe it's a
> very common use case in a low latency system.
> *Proposed Solution*
> Provide option to user to specify `callTimeout`/`requestTimeout`
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
