[
https://issues.apache.org/jira/browse/HTTPCORE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-573.
----------------------------------------
Resolution: Fixed
Fix Version/s: 5.0-beta8
4.4.12
Fixed in 4.4.x and master.
Oleg
> 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
> Fix For: 4.4.12, 5.0-beta8
>
> 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]
