You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2019/06/27 15:21:00 UTC
[jira] [Moved] (HTTPCORE-581) Wrong time calculation for read
operation deadlines when using kept-alive connections
[ https://issues.apache.org/jira/browse/HTTPCORE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski moved HTTPCLIENT-1998 to HTTPCORE-581:
--------------------------------------------------------
Fix Version/s: (was: 5.0 Beta5)
5.0-beta8
Affects Version/s: (was: 5.0 Beta4)
5.0-beta7
Component/s: (was: HttpClient (async))
HttpCore NIO
Workflow: classic default workflow (was: Default workflow, editable Closed status)
Key: HTTPCORE-581 (was: HTTPCLIENT-1998)
Project: HttpComponents HttpCore (was: HttpComponents HttpClient)
> Wrong time calculation for read operation deadlines when using kept-alive connections
> -------------------------------------------------------------------------------------
>
> Key: HTTPCORE-581
> URL: https://issues.apache.org/jira/browse/HTTPCORE-581
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 5.0-beta7
> Reporter: Joan Balagueró
> Priority: Major
> Fix For: 5.0-beta8
>
> Attachments: keep_alive.txt
>
>
> Presently the internal data channel calculates the deadline of read operation based on the last read access. Naturally the last read operation timestamp on a persistent (kept-alive) HTTP connection usually points back at the previous message exchange
> [https://github.com/apache/httpcomponents-core/blob/master/httpcore5/src/main/java/org/apache/hc/core5/reactor/InternalChannel.java#L64]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org