Port forwarding: remote server closes connection, but sshj does not close connection to client

TLDR; I have a failing unit test that I think points at a legitimate bug: [https://github.com/tsoiland/sshj/commit/4a7afbcc3ca14fc091a90f9faf74ce146c307328](https://github.com/tsoiland/sshj/commit/4a7afbcc3ca14fc091a90f9faf74ce146c307328)

I originally had a problem running docker exec (http api) through sshj. From what I've been able to gather it streams data back in the http response and probably doesn't know the content length when it writes the response headers, so the client has to wait until the connection is closed by the server.

When I try to tunnel this through sshj the connection between my http client and sshj is never closed and therefore my http client waits forever.

This works with a direct connection to docker's http server.

It also works tunnelled through openssh-client and I can see the FIN, ACKs on both sides of the tunnel with wireshark.