[jira] [Resolved] (TS-3584) SPDY and H2 requests should not trigger connection keep-alive processing

["Susan Hinrichs (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Susan Hinrichs resolved TS-3584.
--------------------------------
    Resolution: Fixed

I explicitly added the "Connection: close" header for both SPDY and H2.  We have been exercising the SPDY case in production.  I tested the H2 in my dev environment.

This seemed like the least code change.  We may want to revisit this solution as we better understand the relations between SPDY/H2 and underlying HTTP/1.x processing.

> 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)