Signature failure for folder with ampersand in name

[cyberduck]

a40a367 created the issue

If I create a S3 Bucket in EU Central / Frankfurt and a subfolder contains a special character (e.g. &) like:

NameOfBucket
                 -> FolderWith&InTheName
                                      ->Files

Cyberduck didn't display the files. I can upload new ones but there are only visible in the S3 webview or aws cli.
A Bucket in Ireland or US with the same folders and files is displayed correct.
So maybe a problem with the new AWS-SHA256?

Thanks

---

Attachments

• s3-aws.png (12.8 KiB)
• s3-cyberduck.png (11.6 KiB)

[cyberduck]

@dkocher commented

I can reproduce this issue with bucket in eu-central.

[cyberduck]

@dkocher commented

• Sample response from eu-central for GET /?max-keys=1000&prefix=&/&delimiter=/ HTTP/1.1[\r][\n]

<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>cyberduck-eucentral</Name><Prefix></Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated><CommonPrefixes><Prefix>&amp;/</Prefix></CommonPrefixes></ListBucketResult>[\r][\n]

Compared with a properly escaped request

• Sample response from us-east-1 for GET /?max-keys=1000&prefix=%26%2F&delimiter=%2F HTTP/1.1[\r][\n]

<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>cyberduck-useast</Name><Prefix>&amp;/</Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated><Contents><Key>&amp;/</Key><LastModified>2015-07-02T14:17:29.000Z</LastModified><ETag>&quot;d41d8cd98f00b204e9800998ecf8427e&quot;</ETag><Size>0</Size><Owner><ID>9e566b20db6d815be833c75619604c94f421d600420bba9d92214ad250dfdbe1</ID><DisplayName>_</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents><Contents><Key>&amp;/f</Key><LastModified>2015-07-02T14:17:32.000Z</LastModified><ETag>&quot;d41d8cd98f00b204e9800998ecf8427e&quot;</ETag><Size>0</Size><Owner><ID>9e566b20db6d815be833c75619604c94f421d600420bba9d92214ad250dfdbe1</ID><DisplayName>_</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents></ListBucketResult>[\r][\n]

The error is indeed that when using AWS4 authorization the request line is rewritten and not properly URI encoded.

[cyberduck]

@dkocher commented

In 07482a9 from upstream 925da07.

[cyberduck]

@dkocher commented

Pending changeset in (https://bitbucket.org/jmurty/jets3t/pull-requests/36/use-raw-query-string-from-uri-for/diff).