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
I'm working on bigger tool using forwarding and I have to reuse local listener to open multiple channels on single session to different remote hosts/ports.
Unfortunately after channel is closed SSH connection is left in some bogus state:
When 1 is called on first channel opened then every new channel opened after that immediately leaves block 2. I can reproduce it using provided forward.p6 file.
First request:
$ curl -v -H "Host: www.bash.org" http://127.0.0.1:8888/
* Trying 127.0.0.1:8888...
* Connected to 127.0.0.1 (127.0.0.1) port 8888 (#0)
> GET / HTTP/1.1
> Host: www.bash.org
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Mon, 14 Oct 2024 20:28:20 GMT
< Server: Apache/2.2.15 (CentOS)
< Last-Modified: Tue, 14 Dec 2010 19:47:34 GMT
< ETag: "28148c-0-497641785a180"
< Accept-Ranges: bytes
< Content-Length: 0
< Connection: close
< Content-Type: text/html; charset=UTF-8
<
* Closing connection 0
Second request:
$ curl -v -H "Host: www.bash.org" http://127.0.0.1:8888/
* Trying 127.0.0.1:8888...
* Connected to 127.0.0.1 (127.0.0.1) port 8888 (#0)
> GET / HTTP/1.1
> Host: www.bash.org
> User-Agent: curl/7.74.0
> Accept: */*
>
* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact
curl: (52) Empty reply from server
When not closing channel next connections work fine (of course until session limit is reached).
The text was updated successfully, but these errors were encountered:
Also there is some oddity here. Commenting out LAST $connection.close causes infinite wait on $session.forward. I completly do not see the correlation, but it is 100% reproducible.
I'm working on bigger tool using forwarding and I have to reuse local listener to open multiple channels on single session to different remote hosts/ports.
Unfortunately after channel is closed SSH connection is left in some bogus state:
When
1
is called on first channel opened then every new channel opened after that immediately leaves block2
. I can reproduce it using provided forward.p6 file.First request:
Second request:
When not closing channel next connections work fine (of course until session limit is reached).
The text was updated successfully, but these errors were encountered: