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

Invalid signature for path with * #9914

Closed
cyberduck opened this issue Apr 7, 2017 · 5 comments
Closed

Invalid signature for path with * #9914

cyberduck opened this issue Apr 7, 2017 · 5 comments
Assignees
Labels
bug fixed low priority s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

bab1498 created the issue

Using Amazon S3 system, if I try to create or access a folder titled "!**Team Photo from OCP 2014", I get an error message

The request signature we calculated does not match the signature you provided.". The objects in the folder are not accessible and the error repeats. Feels like a key signing error for that specific request as the access key works with all the other many objects I store in S3.

Data from view log drawer:

PUT /**Team%20Photo%20from%20OCP%202014/ HTTP/1.1
Date: Fri, 07 Apr 2017 13:42:19 GMT
Expect: 100-continue
Content-Type: application/x-directory
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-storage-class: REDUCED_REDUNDANCY
Host: jflowers.new-bucket.s3.amazonaws.com
x-amz-date: 20170407T134219Z
Authorization: ********
Content-Length: 0
Connection: Keep-Alive
User-Agent: Cyberduck/5.4.0.23761 (Mac OS X/10.12.4) (x86_64)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I can reproduce this issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10677 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#10649 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In ac09709.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone deleted

@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 low priority s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants