You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLDR; I have a failing unit test that I think points at a legitimate bug: tsoiland@4a7afbc
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.
The text was updated successfully, but these errors were encountered:
I realized while doing some more debugging that my problem is with local port forwarding, not remote like in my linked pull request. New unit test with fix in StreamCopier.java: tsoiland@54b2310
I looked at issue Unable to notify remote exec command of an EOF of the stdin #143, but there the problem seems to be the other way around. Also uncommenting the suggested line doesn't help: trans.write(new SSHPacket(Message.CHANNEL_EOF).putUInt32(chan.getRecipient()));
tsoiland
added a commit
to tsoiland/sshj
that referenced
this issue
Jul 12, 2021
TLDR; I have a failing unit test that I think points at a legitimate bug: tsoiland@4a7afbc
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.
The text was updated successfully, but these errors were encountered: