Is there any chance of having https://winscp.net/tracker/1768 'fixed'?
I understand that in this case the fault is not on WinSCP's side, but rather on the server's side. The problem is that it usually happens with old legacy systems, for which we have zero chance of getting a fix.
It wouldn't even be necessary to accept the whole
2xxrange of response codes. Simply accepting
25xwould fix all cases linked in the bug report and still be 'nearly-compliant' with the RFC.
Also, keep in mind that since the
CWDcommand happens under the covers, this is a blocking issue with no possible workaround. This blocks us from using WinSCP at all.
Thanks in advance