fix: handle closed connection errors gracefully #602
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.
Summary
When a client disconnects immediately after connecting (before sending any commands), the server would log multiple error messages that appear alarming but are actually normal FTP client behavior.
Problem
Some FTP clients (like KDE Dolphin, certain Go clients) may:
This resulted in error logs like:
Solution
Detect "use of closed network connection" and "connection reset by peer" errors and handle them as normal disconnects (debug level) instead of errors.
Changes in two code paths:
Before
After
(Only visible when debug logging is enabled)
Test plan
go build ./...succeedsFixes #710
🤖 Generated with Claude Code