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 AWS2 algoritm not allowed any more #10203

Closed
cyberduck opened this issue Jan 20, 2018 · 5 comments
Closed

S3 AWS2 algoritm not allowed any more #10203

cyberduck opened this issue Jan 20, 2018 · 5 comments
Assignees
Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

8e86569 created the issue

cyberduck version: 6.3.5

In previous versions of cyberduck was posible to generate an link to a file in S3 using AWS2 algoritm; but now is not possible, the links are generated with AWS4 algoritm. Then the links are not valid when they are generated for more than 7 days.
So this is the error from S3:

<Error>
<Code>AuthorizationQueryParametersError</Code>
<Message>
X-Amz-Expires must be less than a week (in seconds); that is, the given X-Amz-Expires must be less than 604800 seconds
</Message>
<RequestId>98B36638CCB7B4C6</RequestId>
<HostId>FEE9lxU08MTVYLb4gD6RWC0N4knK2HfkQBvmPfz6cW0QuHcl4RPuJidWOA9a7GxadHNq6WX4bz4=</HostId>
</Error>

In previous version was posible to force the AWS2 algoritm in a file user.config whith this:

but is not working any more.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is according to the documentation and is still supposed to work. Alternatively, use the AWS2 profile.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I can reproduce the issue. Related to #8386.

@cyberduck
Copy link
Collaborator Author

8e86569 commented

No. Not working.
Replying to [comment:2 dkocher]:

This is according to the documentation and is still supposed to work. Alternatively, use the AWS2 profile.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 8d81728.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

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

No branches or pull requests

2 participants