Tweet
I am using v3.1.7 pro.
When I do a text comparison of a pair of files where each is larger than 32768 bytes, the remote file on the FTPS server (implicit ftp, port 990) only shows the first 32,768 bytes.
This results in Beyond Compare reporting the remote file as missing tons of content. If you copy the file locally, then re-deploy it, you will lose all content beyond the 32k mark.
Steps to reproduce:
1) Create a file that is larger than 32k in notepad. I just pasted 1234567890 bunches and bunches of times. I called mine "large.txt".
2) Use an ftp client to send that file to a remote FTPS server. I used SmartFTP.
3) Using the same ftp client, download that file again as "large (2).txt" to make sure it's intact and there are no problems with the ftps server itself. Comparing the files locally shows that they are "binary same". BC does fine if the files are local.
4) Do a file comparison where over the internet, comparing the local "large.txt" to a remote "large.txt" on an Implicit FTPS server.
5) In the remote view, you see only the first 32768 bytes of large.txt.
6) If you copy that file from a folder comparison, it will copy only the first 32k of the file, so if you were to deploy it again, it would actually be incomplete on the server and everything after 32k is lost.
I think I have narrowed this down to it being Beyond Compare, because the ftp server behaves normally with any other file, and still normally with large files over an ftp client like SmartFTP and FileZilla. It just seems like BC is limited to 32k with FTPS?
When I do a text comparison of a pair of files where each is larger than 32768 bytes, the remote file on the FTPS server (implicit ftp, port 990) only shows the first 32,768 bytes.
This results in Beyond Compare reporting the remote file as missing tons of content. If you copy the file locally, then re-deploy it, you will lose all content beyond the 32k mark.
Steps to reproduce:
1) Create a file that is larger than 32k in notepad. I just pasted 1234567890 bunches and bunches of times. I called mine "large.txt".
2) Use an ftp client to send that file to a remote FTPS server. I used SmartFTP.
3) Using the same ftp client, download that file again as "large (2).txt" to make sure it's intact and there are no problems with the ftps server itself. Comparing the files locally shows that they are "binary same". BC does fine if the files are local.
4) Do a file comparison where over the internet, comparing the local "large.txt" to a remote "large.txt" on an Implicit FTPS server.
5) In the remote view, you see only the first 32768 bytes of large.txt.
6) If you copy that file from a folder comparison, it will copy only the first 32k of the file, so if you were to deploy it again, it would actually be incomplete on the server and everything after 32k is lost.
I think I have narrowed this down to it being Beyond Compare, because the ftp server behaves normally with any other file, and still normally with large files over an ftp client like SmartFTP and FileZilla. It just seems like BC is limited to 32k with FTPS?
Comment