[
https://issues.apache.org/jira/browse/HDFS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417080#comment-13417080
]
Daryn Sharp commented on HDFS-3671:
-----------------------------------
Are you sure you tested a non-chunked download w/o a content-length in the
response? If it worked, there should have been a 200s hang at the end of the
transfer, and would mean the http read timeout has been broken...
> 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
> Attachments: h3671_20120717.patch
>
>
> 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
