[TS-3834] Close the client session after sending GOAWAY with errors

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.0.0
• Component/s: HTTP/2
• Assignee: Ryo Okubo
• Reporter: Ryo Okubo
• Created: 12/Aug/15 08:05
• Updated: 08/Sep/16 20:03
• Resolved: 11/Sep/15 14:14

Description

According to Section 5.4.1 of RFC7540 , after sending with error codes, a server must close TCP connection. Current ATS only sends GOAWAY but doesn't close client session.

This behavior can be checked by h2spec with -s 5.4.1 option.

$ ./h2spec -h <host> -p <port> -s 5.4.1
  5.4. Error Handling
    5.4.1. Connection Error Handling
      × Receives a GOAWAY frame
        - After sending the GOAWAY frame, the endpoint MUST close the TCP connection.
          Expected: Connection close
            Actual: Error: Connection closed, but did not receive a GOAWAY Frame.

68 tests, 0 passed, 67 skipped, 1 failed

===============================================================================
Failed tests
===============================================================================

  5.4. Error Handling
    5.4.1. Connection Error Handling
      × Receives a GOAWAY frame
        - After sending the GOAWAY frame, the endpoint MUST close the TCP connection.
          Expected: Connection close
            Actual: Error: Connection closed, but did not receive a GOAWAY Frame.

Issue Links

• blocks: TS-3808 ☂ Testing HTTP/2 features by h2spec
• supercedes: TS-4830 Http2 write_vio.reenable crash