> On Nov 19, 2017, at 5:24 PM, Christian Schmitz
> wrote:
>
> Well, I think you could move to CURLSFileInfoMBS class for FTP listing
> instead.
> It does parsing better than FTPParse class.
Thank you. I tried your example. It works great with FTP.
> Am 19.11.2017 um 23:37 schrieb Jerry Fritschle :
>
> I am still at this point: that if I try to rerun an interrupted batch upload
> with SFTP, it will corrupt any file that is already complete, when it tries
> to append. So I have thought of a couple of workarounds.
I am still at this point: that if I try to rerun an interrupted batch upload
with SFTP, it will corrupt any file that is already complete, when it tries to
append. So I have thought of a couple of workarounds.
One of these was to get a directory listing in advance, parse the sizes, and
skip
Okay, in the light of day and being a little fresher, I see what is going on.
Under SFTP, the resumption DOES work correctly, and the large test file,
intentionally broken, is completed.
What fails is that, unlike FTP, if the file is already complete on the server,
it gets corrupted in the
>
> From what I’m gathering about SFTP, I am wondering whether this is even
> possible with libcurl. It is my understanding that its SFTP command
> vocabulary is relatively basic and limited. Using built-in SFTP in the
> terminal, I am successful with the “reput” command. So calling that
I am working on adding SFTP compatibility to my products that, through
CURLSMBS, employ FTP. I am testing against an up-to-date CrushFTP server that
I administer myself, which is accessible from the internet.
For my needs, I have worked everything out except for successfully being able
to