[
https://issues.apache.org/jira/browse/TS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682331#comment-13682331
]
Alan M. Carroll commented on TS-1776:
-------------------------------------
I think that might be ugly, this isn't the only change in that area and they're
interrelated. Having slept on it, I think the best choice is to set the source
to SOURCE_CACHE if the range transform is the only range. You want
SOURCE_TRANSFORM if it's not an internal transform.
> 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
> Affects Versions: 3.2.4
> Reporter: William Bardwell
> Assignee: William Bardwell
> Priority: Blocker
> Fix For: 3.2.5
>
>
> 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
