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

S3 pre-signed URL doesn't work #10886

Closed
cyberduck opened this issue Nov 27, 2019 · 4 comments
Closed

S3 pre-signed URL doesn't work #10886

cyberduck opened this issue Nov 27, 2019 · 4 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

0bc3b97 created the issue

The S3 pre-signed URL can't be visited. Error like below:

<Error>
<Code>InvalidRequest</Code>
<Message>
The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
</Message>
<RequestId>FEAC288AB9E9765C</RequestId>
<HostId>
lMFCiJnwzWpEX9glXBVNl/kVOCq35IjhiSvO814mkQN6dTMNP7QhGYH3wlN6JICu2b8D7QHq8n4=
</HostId>
</Error>
@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot reproduce this error. Can you share an example of a pre-signed URL that is showing this error.

@cyberduck
Copy link
Collaborator Author

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Do you use the S3 China (Beijing) connection profile from (https://cyberduck.io/s3/)?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 3d633c6.

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

No branches or pull requests

2 participants