[
https://issues.apache.org/jira/browse/TS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640526#comment-14640526
]
ASF subversion and git services commented on TS-3584:
-----------------------------------------------------
Commit 0b160a7f3e438101a0be3937ad3e92ff186b614e in trafficserver's branch
refs/heads/master from shinrich
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=0b160a7 ]
Revert "TS-3584: SPDY and H2 requests should not trigger connection keep-alive."
This reverts commit dda6814f07ee59c9e3e452a649e6e7f80906457d.
Conflicts:
CHANGES
> SPDY and H2 requests should not trigger connection keep-alive processing
> ------------------------------------------------------------------------
>
> Key: TS-3584
> URL: https://issues.apache.org/jira/browse/TS-3584
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, HTTP/2, SPDY
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 6.0.0
>
>
> For HTTP 1.1 the default value for the Connection header is keep-alive. So
> all requests coming from SPDY and H2 dutifully set up the HttpClientSession
> for potential future reuse.
> However, SPDY and H2 will create a new FetchSM request (and related
> HttpClientSession) for every HTTP request, so the HttpClientSession will
> never be reused.
> This results in unnecessary complexity and inefficiency. I'm seeing some
> crashes in SPDY start up that could be related to VC freeing race conditions.
> I'd like to tidy this up to remove one element from the equation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
