[
https://issues.apache.org/jira/browse/TS-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704269#comment-13704269
]
Bryan Call commented on TS-1962:
--------------------------------
commit d230caedcc0e63a9cf21bf3ffeda648a844ad562
Author: Bryan Call <[email protected]>
Date: Tue Jul 9 23:50:47 2013 -0700
TS-1962 - close the connection to the server if doing a POST/PUSH request
and the POST keep-alive option is not on
> keepalive post issues
> ---------------------
>
> Key: TS-1962
> URL: https://issues.apache.org/jira/browse/TS-1962
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Thomas Jackson
> Assignee: Bryan Call
> Fix For: 3.3.5
>
>
> I've been running ATS at the edge with keepalive enabled. After some digging
> I found that ATS creates new connections (by default) for all post requests,
> instead of re-using a connection. The comment in the code looks like this was
> (is?) because of some race condition inside ATS. I noticed that there is a
> config option (proxy.config.http.keep_alive_ post_out) which enables the
> connection re-use for post requests, and it seems to work. Does anyone have
> any knowledge/experience with this configuration option? Or anything about
> this race condition?
> In addition to the possible bug, if you leave it on the default (new
> connection per post) it returns the connection to the keep alive pool and I
> notice 10x latency on all post requests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
