You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2014/04/03 01:51:18 UTC

[jira] [Resolved] (TS-2589) Headers delayed until the origin server starts sending content

     [ https://issues.apache.org/jira/browse/TS-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Peach resolved TS-2589.
-----------------------------

    Resolution: Fixed

> Headers delayed until the origin server starts sending content
> --------------------------------------------------------------
>
>                 Key: TS-2589
>                 URL: https://issues.apache.org/jira/browse/TS-2589
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Jack Bates
>            Assignee: James Peach
>             Fix For: 5.0.0
>
>
> If there is a transform (for example a null transform) then the response headers aren't forwarded until the origin server starts sending content. Normally (without a transform) the headers are forwarded as soon as they are done, whether content is available yet or not.
> The headers are sent when the transform calls TSVConnWrite() and the transform is called at the end of the headers/start of the content. But it's not called if the available content is empty. A possible fix is to call the transform at the start of the content whether content is available yet or not. This doesn't affect a buffered transform which can still delay and update the headers until it calls TSVConnWrite()



--
This message was sent by Atlassian JIRA
(v6.2#6252)