[
https://issues.apache.org/jira/browse/TS-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-3777:
-------------------------------
Attachment: ts-3777-3.diff
I added logic in HttpTransact::initialize_state_variables_from_request to
always initialize client_info.keep_alive to HTTP_NO_KEEPALIVE if the client
request is internal. That should give us broader protection from accidental
keepalive/pipeline logic in the internal case. It should also address TS-3584.
I tested this change with the sets to keep_alive and pipeline_possible that I
added in HttpSM::state_watch_for_client_abort commented out. Daniel's scenario
worked in that case.
I'm leaving the the logic in HttpSM::state_watch_for_client_abort in this patch
though. It makes sense for non-internal requests to not be marked for pipeline
in this scenario as well.
> TSHttpConnect and POST request does not fire TS_VCONN_READ_COMPLETE nor
> TS_VCONN_EOS
> ------------------------------------------------------------------------------------
>
> Key: TS-3777
> URL: https://issues.apache.org/jira/browse/TS-3777
> Project: Traffic Server
> Issue Type: Bug
> Components: TS API
> Reporter: Daniel Vitor Morilha
> Assignee: Susan Hinrichs
> Labels: yahoo
> Fix For: 6.1.0
>
> Attachments: ts-3777-2.diff, ts-3777-3.diff, ts-3777.diff
>
>
> When using TSHttpConnect to connect to ATS itself (internal vconnection),
> sending a POST request and receiving a CHUNKED response. ATS does not fire
> neither TS_VCONN_READ_COMPLETE nor TS_VCONN_EOS.
> Trying to close the vconnection from the plug-in after receiving the last
> chunk ("\r\n0\r\n") results into the PluginVC repeating the following message:
> {noformat}
> [Jul 14 21:24:06.094] Server {0x7ffff7fbe800} DEBUG: (pvc_event) [0] Passive:
> Received event 1
> {noformat}
> I am glad to provide an example if that helps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
