fix(sftp): resolve connection poisoning with enterprise SFTP servers #4153
+193
−46
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.
Description
This PR fixes SFTP connection poisoning and concurrent race conditions when using the SFTP binding with enterprise SFTP servers like Axway MFT.
Changes
Lock()instead ofRLock()for full operation serialization - Prevents concurrent operations that confuse strict SFTP serversshouldReconnect()error classification - Properly detectsStatusErrortypes viaerrors.As()to avoid unnecessary reconnection attemptsshouldReconnect()logicIssue reference
Fixes #4078
Checklist