[jira] [Updated] (TS-3834) Close a client session after sending GOAWAY with errors

["Bryan Call (JIRA)" <ji...@apache.org>]

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

Bryan Call updated TS-3834:
---------------------------
    Backport to Version: 6.0.0

> Close a client session after sending GOAWAY with errors
> -------------------------------------------------------
>
>                 Key: TS-3834
>                 URL: https://issues.apache.org/jira/browse/TS-3834
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP/2
>            Reporter: Ryo Okubo
>            Assignee: Ryo Okubo
>             Fix For: 6.1.0
>
>
> According to [Section 5.4.1 of RFC7540|https://tools.ietf.org/html/rfc7540#section-5.4.1] , 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|https://github.com/summerwind/h2spec] with -s 5.4.1 option.
> {noformat}
> $ ./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.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)