[Cyberduck-trac] [Cyberduck] #9378: S3 Creating New Folders with SSE Restriction Fails

[Cyberduck]

#9378: S3 Creating New Folders with SSE Restriction Fails
-----------------------+-------------------
    Reporter:  jmgtan  |      Owner:
        Type:  defect  |     Status:  new
    Priority:  normal  |  Milestone:
   Component:  core    |    Version:  4.8.3
    Severity:  normal  |   Keywords:
Architecture:          |   Platform:
-----------------------+-------------------
 Steps to replicate:

 1. Create a new bucket and apply the bucket policy from this page:
 http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html
 2. Connect using Cyberduck and enable server side encryption in the
 preferences.
 3. Try to upload a normal file and it should work.
 4. Create a new folder and it would fail.

 Creating a new folder via the AWS CLI works:

 aws s3api put-object --server-side-encryption AES256 --key test/ --bucket
 <bucketName>

 Setting the s3.metadata.default to include the encryption header doesn't
 work either. It seems like creating a new folder doesn't include the x
 -amz-server-side-encryption header.

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