[
https://issues.apache.org/jira/browse/TS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613377#comment-13613377
]
William Bardwell commented on TS-1776:
--------------------------------------
It seems like the changes to try to add fancy range support left behind the old
transform code, but missing the handling for calculating the proper
content-length. And the full content length is used to start writing the data,
and the change_response_headers() now unconditionally does multipart stuff.
Also the code in HttpTunnel calculates read_start_pos and does a do_io_pread()
to seek even when the fix has claimed that pread() shouldn't be used, and the
RangeTransform code is going to try to do the seeking by skipping. (So now the
start skip amount get skipped twice.)
> Range requests not working right in 3.2.4
> -----------------------------------------
>
> Key: TS-1776
> URL: https://issues.apache.org/jira/browse/TS-1776
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: William Bardwell
>
> With the patch in 3.2.4 for TS-1575 that tries to turn off the new range
> code, range requests aren't work right for me. The responses have all of the
> multi-part header markings, but the Content-Length and Content-Range headers
> should be used for single range requests. Also when I do a range that starts
> > 0, the content is wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
