Regarding the sequence violation when using scripts in winsc

When connecting to the SFTP server in winscp, (Using scripts) because the SFTP server will output an error and then terminate. :cry:

According to the vendor who provided the SFTP server, when scripts of winscp are used,
errors will occur in the SFTP server because the data transmission in the winscp will violate the sequence.

After winscp sent the files using the ‘get’ command, the ‘close’ request was submitted.
Without waiting for the reply from the server, the transport channel terminated.
Due to that reason, errors occurred in the server because the client did not receive a normal termination of the file closing.
Is this a bug of winscp in which the close request was submitted and the reply was not received . Is there a way to avoid this problem?

The following are the scripts and commands.

"C:\Program Files\WinSCP\WinSCP.com" /script=d:\sftp_test\test.scp /log=d:\sftp_test\test.log

test.scp ‘s details
open XXXXX@XXXXXX
get XXXXXX.txt
close
exit

Please attach a full log file showing the problem (using the latest version of WinSCP).

Thank you for your reply.

Please allow me to send the log to you.
I generated it using winscp5.1.7.
The log's output destination and the script name is different from those in the enquiry I posted above.
However, the problem still remains the same.

script　details
open XXXXXXXX@XXXXXXX
lcd d:\

get /edidata/TST00003S/TST003SS
close
exit

Ok, I see the point now. It's true that WinSCP does not wait for confirmation of "file close" request. But I'm not ware of any obligation to do that. So I do not think this "violation" of anything.

Thank you for your reply.

According to the vendor’s reply, if the product has been created based on RFC4254 ,draft-ietf-secsh-filexfer-02 and etc, it seems that the SSH_FXP_CLOSE message should return a reply.

Which standard does winscp base on to determine whether to wait or not for a reply from the message, or whether to sync or not using a script command?

Is winscp going to remain as its current state of not waiting for a reply, without an update in the future?

According to the vendor’s reply, if the product has been created based on RFC4254 ,draft-ietf-secsh-filexfer-02 and etc, it seems that the SSH_FXP_CLOSE message should return a reply.

Indeed. But I do not see any requirement that a client needs to wait for it. No other server ever had a problem with this.

Is winscp going to remain as its current state of not waiting for a reply, without an update in the future?

Unless I get convinced that it is a bug.

I feel that Winscp is a great software. :D
However, it does not work well with our server. Therefore, we are considering using other client softwares.
Thank you for your reply.