On Tue, 6 Sep 2022 13:56:15 GMT, Conor Cleary <[email protected]> wrote:
> **Issue** > When using HTTP/2 with the HttpClient, it can often be necessary to close an > idle Http2 Connection before a server sends a GOAWAY frame. For example, a > server or cloud based tool could close a TCP connection silently when it is > idle for too long resulting in ConnectionResetException being thrown by the > HttpClient. > > **Proposed Solution** > A new system property, `jdk.httpclient.idleConnectionTimeout`, was added and > is used to specify in Milliseconds how long an idle connection (idle > connections are those which have no currently active streams) for the > HttpClient before the connection is closed. IMHO, it would be great to use the same property as for HTTP/1 connections: `jdk.httpclient.keepalive.timeout` People are already expecting it to work with HTTP/2, but to everyone's surprise it doesn't. It would also be nice to support `jdk.httpclient.connectionPoolSize` for HTTP/2 as well, again to avoid surprises. Neither of these properties reference either HTTP/1 or HTTP/2 in their names, so should work for all kinds of connections. ------------- PR: https://git.openjdk.org/jdk/pull/10183
