joerg1985

@VietND96 I don't think this should be merged, see my concerns above in https://github.com/SeleniumHQ/selenium/pull/14432#issuecomment-2328743898

I just stumbled into another usecase for this, the `org.openqa.selenium.netty.server.SeleniumHandler` does not cancel the currently running http request after the client has gone away. This usually happens in case of...

Okay, there is no need to keep the session alive, the read timeout of the node is identical to the session timeout. And the driver blocks concurrent command execution until...

I could create a PR for this in case you think this makes sense, but i do not want to waste time on it in case you think this is...

I have create a PR for this with one change, i have extended the HttpClient interface. The HttpHandler is used in a lot of areas that do not benefit from...

The HttpClient has been extended with the new method.

@pujagani i think i can fix this the next days, we are sending a close message and do not wait for the close message from the other end before shutting...

@kherath17 this should be fixed with the next release. You could try to upgrade to the next nightly build to confirm this.

> But what if an endpoint returns a malformed response, a status code which was not expected. By mocking the the responses we can easily test the non happy path,...

@VietND96 sorry i don't know enought to really review the changes in this PR. From the comment in the code [here](https://github.com/SeleniumHQ/selenium/blob/751bacb6bc934436ec9dec2416a022d8d577e30a/java/src/org/openqa/selenium/grid/data/DefaultSlotMatcher.java#L148-L152) and after looking into the issue #14461 i am...