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
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>
The text was updated successfully, but these errors were encountered:
@dkocher commented
In faea226.
Sorry, something went wrong.
dkocher
No branches or pull requests
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
The Ceph/S3 server is returning
The text was updated successfully, but these errors were encountered: