Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

how does cyberduck decide where to resume an upload from? #9725

Closed
cyberduck opened this issue Oct 5, 2016 · 1 comment
Closed

how does cyberduck decide where to resume an upload from? #9725

cyberduck opened this issue Oct 5, 2016 · 1 comment
Labels
bug ftp FTP Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

6ba74e0 created the issue

I'm using cyberduck to test my ftp server and make sure users can resume their partial uploads okay.

I start an upload of a 900 MB file, and let it go to 200 MB and hit stop.

I do an ls on my server and see the partial file is there and it size 200 MB.

Then I hit resume in cyberduck and progress bar start going again but it doesn't start from 200 MB it start from 100 MB! So all the wrong bytes are being appended to my file on the server.

Does cyberduck have it's own internal integer of what byte to resume from? Or does it get the current size from the server for this value?
@cyberduck
Copy link
Collaborator Author

@dkocher commented

The file size to resume from is determined from the file attributes the server returns for the existing file.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug ftp FTP Protocol Implementation worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck