Skip to content
New issue

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

Signature failure for folder with ampersand in name #8904

Closed
cyberduck opened this issue Jul 2, 2015 · 4 comments
Closed

Signature failure for folder with ampersand in name #8904

cyberduck opened this issue Jul 2, 2015 · 4 comments
Assignees
Labels
bug fixed s3
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 2, 2015

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 2, 2015

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 2, 2015

@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
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 3, 2015

@dkocher commented

In 07482a9 from upstream 925da07.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 18, 2016

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed s3
Projects
None yet
Development

No branches or pull requests

2 participants