[
https://issues.apache.org/jira/browse/TS-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911888#comment-13911888
]
ASF GitHub Bot commented on TS-2589:
------------------------------------
GitHub user jablko opened a pull request:
https://github.com/apache/trafficserver/pull/49
TS-2589 Don't hold up the response until the server starts sending conte...
...nt
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jablko/trafficserver TS-2589
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/49.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #49
----
commit c42e983b9a2cd4ed33d37f18b46a4df997f0c4b8
Author: Jack Bates <j...@nottheoilrig.com>
Date: 2014-02-25T18:31:35Z
TS-2589 Don't hold up the response until the server starts sending content
----
> 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
>
> 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.1.5#6160)
