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

Malformed request during multipart upload #9755

Closed
cyberduck opened this issue Nov 7, 2016 · 2 comments
Closed

Malformed request during multipart upload #9755

cyberduck opened this issue Nov 7, 2016 · 2 comments
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Milestone

Comments

@cyberduck
Copy link
Collaborator

0c6eac0 created the issue

Hello,

I'm using Cyberduck against an s3 server we have built as part of our data service offering at Igneous Systems. When I attempt to issue a multipart upload using any object >=200MB, the upload hangs toward the end of the upload. Through request logging we can see this is actually due to a malformed request from Cyberduck:

request-out: POST /RMF-container//RMF-container/ice/Anaconda2-4.2.0-MacOSX-x86_64.pkg?uploadId=825e823b7f8abe4e912b4c6ce63e6934
Elapsed_Time: 2.467971ms
HTTP_Status_Code: 404
X-Content-Type-Options: nosniff
X-Amz-Request-Id: 0-16-9e2e6a2f177f772ea0b2221110e2069a
Content-Type: text/plain; charset=utf-8

Note the path is wrong as the bucket name is repeated twice. Because of this we can't find the upload and fail the request. The bucket name should be listed only once in the request.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The issue is caused by a malformed reply to the initiate multipart upload request. The Key in InitiateMultipartUploadResult should not include the bucket name. Refer to http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadInitiate.html#mpUploadInitiate-responses

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@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.
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant