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

MD5 checksum mismatch error #6117

Closed
cyberduck opened this issue Jul 29, 2011 · 14 comments
Closed

MD5 checksum mismatch error #6117

cyberduck opened this issue Jul 29, 2011 · 14 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 29, 2011

e2d9c90 created the issue

I am using Cyberduck on Mac, it works fine with swift, but with S3(swift3) when i try to create some object it gives MD5 checksum mismatch error, even though object creation is successfull.

I tried to trace the checksum swift generating at server side, its matching with what cyberduck is complaining mismatch. I think there is some issue with cyberduck on Mac for S3, with windows it works fine with both swift and S3.

I am not sure about cyberduck version, how to check for the version?


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 29, 2011

@dkocher commented

Use the menu Cyberduck → Check for Update….

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 31, 2011

@dkocher commented

I have never tested against a swift3 endpoint. Can you post the transcript from the log drawer (Transfer window).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 31, 2011

@dkocher commented

Same issue in OpenStack Launchpad.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

e2d9c90 commented

Replying to [comment:1 dkocher]:

Use the menu Cyberduck → Check for Update….

Cyberduck version is 4.0.1

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

e2d9c90 commented

Replying to [comment:3 dkocher]:

I have never tested against a swift3 endpoint. Can you post the transcript from the log drawer (Transfer window).
I have attached the screenshot of transfer window.
As you can see file is uploaded but it still gives md5 error.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

@dkocher commented

The response is missing a ETag header.

Loading

@cyberduck cyberduck closed this Aug 1, 2011
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

@dkocher commented

Actually as of 7579d6c we already check if the ETag header is missing and don't compare if so. Therefore I suppose there is actually an ETag header included in the response that has the value null.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

e2d9c90 commented

Replying to [comment:8 dkocher]:

Actually as of 7579d6c we already check if the ETag header is missing and don't compare if so. Therefore I suppose there is actually an ETag header included in the response that has the value null.

I wonder how its working on windows then?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

@dkocher commented

Replying to [comment:9 gaurav]:

Replying to [comment:8 dkocher]:

Actually as of 7579d6c we already check if the ETag header is missing and don't compare if so. Therefore I suppose there is actually an ETag header included in the response that has the value null.

I wonder how its working on windows then?

I can't explain any difference. We use the very same core library on both platforms and it should behave the same.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

@dkocher commented

To compare we would need the transcript from the log drawer of the Transfers window.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

e2d9c90 commented

Replying to [comment:11 dkocher]:

To compare we would need the transcript from the log drawer of the Transfers window.

Ok on windows i am using 4.1. Its working with 4.1.
When i upgraded to 4.1 on Mac, its also working their.
Its failing with earlier versions on both Mac and Windows, with the same error as i mentioned earlier.
Is their any fix regarding this gone in 4.1.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 1, 2011

@dkocher commented

Replying to [comment:12 gaurav]:

Replying to [comment:11 dkocher]:

To compare we would need the transcript from the log drawer of the Transfers window.

Ok on windows i am using 4.1. Its working with 4.1.
When i upgraded to 4.1 on Mac, its also working their.
Its failing with earlier versions on both Mac and Windows, with the same error as i mentioned earlier.
Is their any fix regarding this gone in 4.1.

That explains it, yes. Version 4.1 was the first release to include the patch in 7579d6c.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2015

f19f995 commented

problems with native openstack swift just in windows

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2015

@dkocher commented

Replying to [comment:15 aivaras.sukackas]:

problems with native openstack swift just in windows
Please open a new issue with the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows.

Loading

@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