Re: LOG of succes download with replacement error code 426 to 110
OK, I'll see if more people ask for this hack.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- buranded
LOG of succes download with replacement error code 426 to 110
log
- buranded
Right, command connection was not losted.
I can repeat this test and logs with my replacement "426" to "110".
I can repeat this test and logs with my replacement "426" to "110".
- martin
Re: log
OK I see. WinSCP does not reconnect, because the FTP connection is actually not closed.
- buranded
log
log
- martin
Re: Buggy FTP server
Please attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
- buranded
Solution
Because our traffic going through our Debian 8 firewall, I can substitute text within TCP-sessions on the fly.
I just used
According to:
https://github.com/rgerganov/nfqsed
This is a very hacky unusual solution, but now WinSCP reconnects and resuming download quickly and quietly.
Please add to WinSCP ability to ignore 426 error and autoresuming download.
I just used
nfqsed to change 426 error code to 110 "comment".
iptables -A INPUT -p tcp -s %BUGGY_FTP_IP% --sport 21 -j NFQUEUE --queue-num 0
/root/nfqsed/nfqsed -s /"426 Cannot RETR. EAccessViolation"/"110 Cannot RETR. EAccessViolation" > /dev/null 2>&1 &
According to:
https://github.com/rgerganov/nfqsed
This is a very hacky unusual solution, but now WinSCP reconnects and resuming download quickly and quietly.
Please add to WinSCP ability to ignore 426 error and autoresuming download.
- buranded
Buggy FTP server
We have one buggy FTP-server and no way to fix it.
Periodically its crashes on downloading file and sent attached error.
Another FTP-clients such as FileZilla reconnects quickly and quietly and resuming download,
but WinSCP stops fatal.
Periodically its crashes on downloading file and sent attached error.
Another FTP-clients such as FileZilla reconnects quickly and quietly and resuming download,
but WinSCP stops fatal.