Uploads of large objects to Oracle Storage Cloud Service fail with 400 error reply

[cyberduck]

5d2bd01 created the issue

We were trying to certify Cyberduck with Oracle Storage Cloud Services and found out that for smaller object uploads works fine, but larger objects, typically > 3GB uploads always fails with an error to retry/continue. From our systems only about 1 GB file uploads worked successfully. Our work flow demands upwards of 50 to 60 GB single file/object upload to be successful, which unfortunately we have not had luck with.

A large object download also gave up problems (about 10 GB).

[cyberduck]

@dkocher commented

Possibly related to #9131. Although this ticket only affect files greater than 100GB.

[cyberduck]

@dkocher commented

Please post 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

[cyberduck]

@dkocher commented

Please update to the latest snapshot build available when testing again.

[cyberduck]

5d2bd01 commented

There was nothing logged to the console/window when I try the upload of a 3.2 GB file. I get a screen that pops up that says the command failed and gives me an option to continue. And if I do, it retries the upload and fails.

The upload never succeeds.

[cyberduck]

@dkocher commented

Surely the transfer log drawer contains the HTTP transcript. Please attach.

[cyberduck]

@dkocher commented

Would it be possibly to activate our identity domain again [1] which would allow us to assist you in testing.

[1] Identity Domain: chiterategmbhtrial85243

[cyberduck]

@dkocher commented

Handled in case CD-52.

[cyberduck]

@dkocher commented

Fixed stream progress reset in b69f593 for failed segments.

[cyberduck]

@dkocher commented

The issue is caused by URI encoded forward slashes in the object name.

[cyberduck]

@dkocher commented

Added test in 12f397b.

[cyberduck]

@dkocher commented

Fix in f5e4c02 from upstream changeset.