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

Pre-Signed URLs contain bad hostname with doubled text #11170

Closed
cyberduck opened this issue Sep 11, 2020 · 5 comments
Closed

Pre-Signed URLs contain bad hostname with doubled text #11170

cyberduck opened this issue Sep 11, 2020 · 5 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

ccf5752 created the issue

The Pre-Signed URL feature is putting a bad hostname in the URL. The name "snap-builds" is doubled at the start of the hostname:

https://snap-builds.snap-builds.s3.amazonaws.com/4.22-patches/builds/6694/sharepointonline-1-422patches6694.zip?AWSAccessKeyId=AKIA2DP4BT3E6U6QYMKY&Expires=1600366990&Signature=eKUZ%2BsT9q9UQv4nXHzqdpOQ4OMY%3D

This is the correct URL:

https://snap-builds.s3.amazonaws.com/4.22-patches/builds/6694/sharepointonline-1-422patches6694.zip?AWSAccessKeyId=AKIA2DP4BT3E6U6QYMKY&Expires=1600366990&Signature=eKUZ%2BsT9q9UQv4nXHzqdpOQ4OMY%3D

The other, non-pre-signed URLs are fine:

cyberduck-bug.png​


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As a workaround set the default hostname s3.amazonaws.com in the bookmark instead of including the bucket with snap-builds.s3.amazonaws.com.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

In 1ba24fb.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

2 similar comments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 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