Half closing of connections when CloseWrite() is available#536
Open
liojacqs wants to merge 1 commit into
Open
Conversation
Clean termination when FIN received on one side but there's data remaining to send from the other side. Fixes an issue discovered in a reverse scenario (client -> chiselServer -> chiselClient -> server), where the client would close connection after sending data, but before the server has finished sending data. Without Chisel, same situation, the server is delaying the close because it still wants to send data, and it closes after having sent it. With Chisel, chiselServer was closing the connection immediately first, preventing the server to send its remaining data.
Author
|
Hello, |
Author
|
Hello, |
jpillora
added a commit
that referenced
this pull request
Jul 16, 2026
- cio.Pipe now propagates half-closes: clean EOF in one direction CloseWrites the destination while the other direction keeps flowing; copy errors still tear down both ends, and Pipe closes both conns before returning (no caller changes needed) - rwcConn delegates CloseWrite to the underlying stream so the SOCKS path half-closes through ssh channels (from PR #548) - exit side dials the target before accepting the ssh channel and rejects it on failure (ssh.ConnectionFailed), so inbound clients see a prompt close instead of a live conn to a dead target - dial is context-bound (tunnel teardown cancels it) with a 30s default timeout, tunable via CHISEL_DIAL_TIMEOUT - adapted from PRs #536/#548/#538; dropped #538's accept-loop serialization and error-text-into-stream reset behavior - e2e: half-close echo (fails on old Pipe, verified), channel rejection for dead targets, prompt local-conn close; unit test for rwcConn CloseWrite delegation Closes md task 19 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix for issue #535 Non graceful closing of remote connection
Use of CloseWrite() instead of Close() in Pipe(), only when available (typically TCP and SSH Channel).
This triggers EOF on the other side instead of totally closing the TCP connection / SSH Channel, leaving the possibility to receive remaining incoming data.
Also removed sync.Once, as when io.Copy finishes we only WriteClose() or Close() the destination of the copy, which triggers io.Copy to end on the other side in cascade.
Also added dst.Close() in both pipeRemote() and handleTCP() as we still need to Close() even with CloseWrite() called in both directions.