[
https://issues.apache.org/jira/browse/HTTPCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803836#comment-16803836
]
ASF subversion and git services commented on HTTPCORE-573:
----------------------------------------------------------
Commit 5c9e64050018dd42d8da9021e620d65117da988e in httpcomponents-core's branch
refs/heads/4.4.x from Julien Coloos
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-core.git;h=5c9e640 ]
HTTPCORE-573 FileContentDecoder don't always enforce the maximum number of
bytes to transfer
Limit the number of bytes read from the internal buffer when
transferring, so that the maximum requested ('count') is respected.
> FileContentDecoder don't always enforce the maximum number of bytes to
> transfer
> -------------------------------------------------------------------------------
>
> Key: HTTPCORE-573
> URL: https://issues.apache.org/jira/browse/HTTPCORE-573
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.4.11
> Reporter: Julien Coloos
> Priority: Trivial
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The FileContentDecoder.transfer function has the 'count' parameter indicating
> the maximum number of bytes to transfer.
> Implementations (LengthDelimitedDecoder and IdentityDecoder) don't respect
> this parameter when getting the data from the internal buffer: in practice
> the whole buffer content is transferred, thus the actual number of bytes
> transferred may exceed the maximum requested by caller.
> Since the way data are read from the buffer can be limited, it is possible to
> respect the requested 'count'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
