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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: HTTP, HTTP/2, SPDY
• Assignee: Susan Hinrichs
• Reporter: Susan Hinrichs
• Created: 05/May/15 17:51
• Updated: 19/Jul/16 19:49
• Resolved: 19/Jul/16 19:49

Description

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.

Issue Links

• depends upon: TS-3612 Restructure Proxy Client Sessions to support transaction oriented Sessions execute transaction hooks and connection oriented Sessions execute session hooks
• is related to: TS-3778 Memory leak caused by the TS-3640.
• is related to: TS-3777 TSHttpConnect and POST request does not fire TS_VCONN_READ_COMPLETE nor TS_VCONN_EOS
• relates to: TS-3640 Drupal auth fails with dda6814f07ee59c over SPDY