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

Hubic mismatch between MD5 and ETag after download #9623

Closed
cyberduck opened this issue Jul 8, 2016 · 2 comments
Closed

Hubic mismatch between MD5 and ETag after download #9623

cyberduck opened this issue Jul 8, 2016 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 8, 2016

6e76f1d created the issue

Hello.
I use cyberduck to connection to hubic, and it works well with little files.
But when I download a 140 MB file, I receive the error:

Mismatch between MD5 hash {1} of downloaded data, and ETag {2} returned by the server

To reproduce:
• start cyberduck
• connect to hubic
• browse folders
• select the file 6D9E8C75C871388C-00-00.mrbak (140MB)
• download it

what happens:
• cyberduck start to download the file
• wait for download...
• at the end of the download, cyberduck send the error

remarks:
• I have compared the downloaded file, with the original file, and they are equal (binary compare with WinMerge)
• I have calculated MD5 of the downloaded file, and it is FEE39042FF0B4C08ADEB0D0B22AD7109
• I have calculated MD5 of the original file, and it is FEE39042FF0B4C08ADEB0D0B22AD7109

System:

  • CyberDuck 5.0.3.20504
  • OAuth 2.0 authentication connection profile (hubiC.cyberduckprofile)
  • Windows 7 Home Premium SP1 64bit

Danilo


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 12, 2016

@dkocher commented

This affects all files stored as large file uploads.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 12, 2016

@dkocher commented

Reopened issue #8861.

Loading

@cyberduck cyberduck closed this Jul 12, 2016
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants