[
https://issues.apache.org/jira/browse/TS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633912#comment-14633912
]
Sudheer Vinukonda commented on TS-3584:
---------------------------------------
Reviewing this fix (related to TS-3778, due to the memory leak it eventually
caused via the subsequent fix TS-3640) - I wonder if the header added to
prevent Keep-Alive for SPDY/H2 streams should not be "Connection: Close", but,
"Proxy-Connection: Close" which would allow that header not be forwarded to the
origin.
I wonder if adding a "Connection: Close", caused TS-3640 in the first place,
since that header may get forwarded to the Origin (?), which is definitely not
what is intended (we don't want to close the outbound connections for all
SPDY/H2 streams).
> 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)
