-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Transmit client treating a successful PASV response as failure #85
base: master
Are you sure you want to change the base?
Conversation
I don't get what this solves and why multiline is a problem? |
@pohmelie I have amended the PR description with more details |
Codecov Report
@@ Coverage Diff @@
## master #85 +/- ##
==========================================
- Coverage 94.04% 93.98% -0.06%
==========================================
Files 7 7
Lines 1695 1695
==========================================
- Hits 1594 1593 -1
- Misses 101 102 +1
Continue to review full report at Codecov.
|
I think at first you should try to get feedback from
Response is valid and works fine with all tools I tried. |
I have now emailed them, thanks. |
@michalc any news? |
I'm getting the same error - but not just in Transmit (also seeing an error while using Cyberduck). Also, the PR from @michalc doesn't seem to fix the issue; still Maybe this should be an issue instead of in here? I am using 0.0.0.0 as the bind IP, and then connecting to 127.0.0.1 - is this maybe related to passive not liking the local IP addresses? I can investigate more next weekend.. |
It will be good if you have time of course. |
This fixes PASV connections on the Transmit client, that doesn't seem to handle the multiline response. An example transcript is below.