[ https://issues.apache.org/jira/browse/TS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan Hinrichs closed TS-3584. ------------------------------ Resolution: Won't Fix Backed out due to memory issue in TS-3778. At some point we should stop sending the useless extra Http transactions for each H2/Spdy request. But it is not a critical issue. > 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)