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

Multipart uploads to non-AWS servers don't work #8677

Closed
cyberduck opened this issue Mar 17, 2015 · 1 comment
Closed

Multipart uploads to non-AWS servers don't work #8677

cyberduck opened this issue Mar 17, 2015 · 1 comment
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
4.7

Comments

@cyberduck
Copy link
Collaborator

8824a7e created the issue

When using a non-AWS S3 server large files are not sent using the multipart upload API. This prevents it from working on files over 5 GB which are required to use multipart uploading.

Here are some details from my environment:

Cyberduck sends

PUT /redacted/alsoredacted.dat HTTP/1.1
Date: Tue, 17 Mar 2015 19:25:24 GMT
Expect: 100-continue
Content-Type: application/octet-stream
Authorization: AWS REDACTED
Content-Length: 8895594496
Host: myserver.com:80
Connection: Keep-Alive
User-Agent: Cyberduck/4.6.5 (17000) (Windows 7/6.1) (x86)

The Ceph/S3 server is returning

HTTP/1.1 400 Bad Request
Date: Tue, 17 Mar 2015 19:25:24 GMT
Server: Apache/2.2.22 (Fedora)
Accept-Ranges: bytes
Content-Length: 80
Connection: close
Content-Type: application/xml
 <?xml version="1.0" encoding="UTF-8"?><Error><Code>EntityTooLarge</Code></Error>
@cyberduck
Copy link
Collaborator Author

@dkocher commented

In faea226.

@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

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.7
Development

No branches or pull requests
2 participants
@dkocher @cyberduck