KB Article #176569
Transfer Mode is set to ASCII but files are send as BINARY
Problem
The following message is observed in the tm.log:INFO [EventQueueWorker-29] com.tumbleweed.st.server.ssh.agent.SftpConnection - ASCII transfers are not supported for the current ssh client version. Binary transfer mode will be used.
Resolution
The received message "ASCII transfers are not supported for the current ssh client version. Binary transfer mode will be used." refers to ST SFTP agent attempting to send the transfer in ASCII mode.
When performing server-initiated uploads using the SFTP protocol SecureTransport cannot always identify the remote operating system when the remote SFTP server has version 3 or less and thus the transfer might be sent as BINARY.
For ASCII mode SFTP transfers, if the remote SFTP server supports the newline extension, SecureTransport correctly converts the end-of-line characters of the file. Otherwise, SecureTransport can be configured to convert the end-of-line characters during server-initiated uploads based on the value of server configuration parameters.
If the value of the Ssh.EndOfLineConversion.enabled server configuration parameter is true, SecureTransport uses the value of the Ssh.EndOfLineConversion.type server configuration parameter as the end-of-line sequence. Valid values are: 0x0A (LF), 0x0D (CR), and 0x0D0A (CRLF).
By default, the value of Ssh.EndOfLineConversion.enabled is false and the value of Ssh.EndOfLineConversion.type is 0x0D0A.