[
https://issues.apache.org/jira/browse/HDFS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415469#comment-13415469
]
Daryn Sharp commented on HDFS-3671:
-----------------------------------
The dilemma is that if the content-length is not defined (and chunking is not
used), then the client doesn't know when it has received all data. The client
hangs after all data is received until the remote server closes the connection.
The server's connection idle timeout is greater than the client's idle timeout
on reads, so the download will fail even if all bytes were received. The other
problem with no content-length is the client won't know if it only received a
partial download.
> ByteRangeInputStream shouldn't require the content length header be present
> ---------------------------------------------------------------------------
>
> Key: HDFS-3671
> URL: https://issues.apache.org/jira/browse/HDFS-3671
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Eli Collins
> Priority: Blocker
>
> Per HDFS-3318 the content length header check breaks distcp compatibility
> with previous releases (0.20.2 and earlier, and 0.21). Like branch-1 this
> check should be lenient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
