[jira] [Commented] (TS-2578) TSVConnAbort(output_vc) doesn't close the client connection

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on TS-2578:
-----------------------------------------------------

Commit ea382fd2c3179b1a00f5bd5cd364cc522768b7dd in trafficserver's branch refs/heads/master from [~nottheoilrig]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ea382fd ]

TS-2578: Close the client connection when you close TransformTerminus

If a transform has sent any content downstream before it decides
to call TSVConnAbort(output_vc) or TSVConnClose(output_vc) then the
client connection doesn't get closed. If TransformTerminus::handle_event()
sends VC_EVENT_ERROR or VC_EVENT_EOS events then the client connection
does get closed, but it only sends these if m_called_user is false.
After any content has been sent downstream, m_called_user is true.

GitHub: This closes #42


> TSVConnAbort(output_vc) doesn't close the client connection
> -----------------------------------------------------------
>
>                 Key: TS-2578
>                 URL: https://issues.apache.org/jira/browse/TS-2578
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Jack Bates
>              Labels: Review
>             Fix For: 5.0.0
>
>
> If a transform has sent any content downstream before it decides to call TSVConnAbort(output_vc) or TSVConnClose(output_vc) then the client connection doesn't get closed.
> If TransformTerminus::handle_event() sends VC_EVENT_ERROR or VC_EVENT_EOS events then the client connection does get closed, but it only sends these if m_called_user is false. After any content has been sent downstream, m_called_user is true.
> One possible solution is to fix the logic in TransformTerminus::handle_event() so it sends these events.



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