Status of Bug 1768

Advertisement

sburbano
Joined:
Posts:
2

Status of Bug 1768

Hi,
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 2xx range of response codes. Simply accepting 25x would fix all cases linked in the bug report and still be 'nearly-compliant' with the RFC.

Also, keep in mind that since the CWD command happens under the covers, this is a blocking issue with no possible workaround. This blocks us from using WinSCP at all.

Thanks in advance

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
36,510
Location:
Prague, Czechia

Re: Status of Bug 1768

I have implemented a compatibility mode that can be enabled using raw session settings FtpAnyCodeForPwd=1.
Note that this is about PWD, not CWD. I assume it was a typo on your side. If not, let me know.

I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.

Reply with quote

sburbano
Joined:
Posts:
2

Re: Status of Bug 1768

Hi Martin

Sorry for the late reply. I have been testing this and it seems to work.
. 2021-10-28 10:44:07.493 Using FTP protocol.
. 2021-10-28 10:44:07.493 Doing startup conversation with host.
> 2021-10-28 10:44:07.508 PWD
< 2021-10-28 10:44:07.508 251 "/XXXXXX" is current directory
. 2021-10-28 10:44:07.508 Getting current directory name.
. 2021-10-28 10:44:07.555 Retrieving directory listing...
Unfortunately, I have not yet been able to do a successful download/upload session due to other peculiarities of our system. I will open follow-up reports if needed.

When (if you can give an estimation) will this arrive to the officially released version?

Best regards

Reply with quote

Advertisement

You can post new topics in this forum