[
https://issues.apache.org/jira/browse/TS-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257066#comment-14257066
]
ASF subversion and git services commented on TS-3189:
-----------------------------------------------------
Commit d66bf29db25798e68f5a13d187a65679d0639b19 in trafficserver's branch
refs/heads/5.2.x from [~sudheerv]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=d66bf29 ]
[TS-3248]: Fix with Susan's help to resolve crash introduced in TS-3189
> Do not start reading data on server to user agent tunnel too soon
> -----------------------------------------------------------------
>
> Key: TS-3189
> URL: https://issues.apache.org/jira/browse/TS-3189
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 5.2.0
>
> Attachments: ts-3189.diff
>
>
> The original logic would set up a do_io_read for max_int in
> HttpSM::attach_server_session.
> However, at this point there still may be things finishing up in the
> user_agent to server tunnel (for posts). We were seeing occasional cases of
> the EOS for the tunnel to user_agent communication being incorrectly
> delivered to the consumer of the user_agent to server tunnel.
> It is sufficient to set up a 0 length read in HttpSM::attach_server_session.
> This will enable the correct handlers to deal with inactivity timeouts. Then
> we can setup the real read in HttpSM::setup_server_read_response_header()
> after we know that the user_agent to origin server tunnel has been taken
> down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
