[Cyberduck-trac] [Cyberduck] #10612: Failure proposed upload exceeds the maximum allowed size

[Cyberduck]

#10612: Failure proposed upload exceeds the maximum allowed size
-------------------------+-------------------------
 Reporter:  MarkBlaise   |         Owner:  dkocher
     Type:  defect       |        Status:  assigned
 Priority:  normal       |     Milestone:  7.0
Component:  cli          |       Version:  6.9.0
 Severity:  normal       |    Resolution:
 Keywords:               |  Architecture:  Intel
 Platform:  Windows 8.1  |
-------------------------+-------------------------

Comment (by donaldduckie):

 Hi Mark & dkocher,

 I am encountering the same issue uploading a 109.58GB file to AWS S3
 Bucket configured with Glacier lifecycle (Transition after 0 day) using
 macOS version of Cyberduck.

 Had the same result as observed by Mark -> ''I could be wrong, but my
 admittedly limited understanding is that the file is uploaded, part by
 part, but in the end Cyberduck executes a PUT of the entire file.''

 Here is the last PUT command executed by Cyberduck before the error
 message is displayed:

 {{{
 PUT /***-to-glacier/***.mov HTTP/1.1
 Date: Tue, 19 Feb 2019 10:29:42 GMT
 Expect: 100-continue
 Content-Type: video/quicktime
 x-amz-content-sha256:
 c0b277c2f37f1e28ce7e774b44735f02f2992023eaa95e9d3e30523b2b88d210
 x-amz-meta-storage-class: GLACIER
 x-amz-meta-version-id: 2szEFFse7EDpQ4h3QmFRhRdtE5AFHTCx
 x-amz-storage-class: GLACIER
 Host: *****.s3.amazonaws.com
 x-amz-date: 20190219T102942Z
 Authorization: ********
 Content-Length: 109582612915
 Connection: Keep-Alive
 User-Agent: Cyberduck/6.9.3.30061 (Mac OS X/10.14.3) (x86_64)
 }}}

 Error message displayed by Cyberduck is the same: Your proposed upload
 exceeds the maximum allowed size. Please contact your web hosting service
 provider for assistance.

 Would be grateful if Cyberduck team could look in this problem.

 Thanks very much.

 Replying to [comment:10 MarkBlaise]:
 > I could be wrong, but my admittedly limited understanding is that the
 file is uploaded, part by part, but in the end Cyberduck executes a PUT of
 the '''''entire file'''''.
 >
 > From the Wasabi log, it seems that the maximum size of a "part" is 5
 GiB.
 >
 > I can say that I have successfully uploaded files as large as 35 GiB,
 perhaps even 90 GiB. But these files are also larger than the 5 GiB
 maximum part size, so it seems that Cyberduck does not always POST the
 entire file - otherwise an upload of any file larger than 5 GiB would
 fail.
 >
 > When and why Cyberduck POSTs the entire file at the end of the upload, I
 cannot say.

--
Ticket URL: <https://trac.cyberduck.io/ticket/10612#comment:12>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows