[ https://issues.apache.org/jira/browse/TS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613388#comment-13613388 ]
William Bardwell commented on TS-1776: -------------------------------------- The fix for TS-1574 (commit 1199e991424d8495a80075718d8ec95a64f3a712) has most of the same fixes but done differently (based on the new range stuff being active in more cases, and a few changes in the 3.3.X code line.) (But it doesn't fix the content-length issues, although they may not happen in the read_while_writer cases since it doesn't have a known content-length anyway.) > 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