You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/09/04 23:35:53 UTC

[jira] [Commented] (TS-1776) Range requests not working right in 3.2.4

    [ https://issues.apache.org/jira/browse/TS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758383#comment-13758383 ] 

Leif Hedstrom commented on TS-1776:
-----------------------------------

Can we nix this one now? Does it function as expect in v4.0.1 ?
                
> 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: Alan M. Carroll
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> 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