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

Jump to bottom

Pre-signed AWS S3 URLs are malformed #10994

Closed
cyberduck opened this issue Mar 17, 2020 · 2 comments
Closed

Pre-signed AWS S3 URLs are malformed #10994

cyberduck opened this issue Mar 17, 2020 · 2 comments
Labels
bug s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

08762be created the issue

In the Copy URL menu for files stored in AWS S3, the Pre-signed URL values contain the bucket name twice in the subdomain field. E.g. if your bucket is called mybucket, the URL becomes https://mybucket.mybucket.s3.amazonaws.com/…, causing SSL certificate errors when opened. Manually deleting the redundant subdomain invalidates the signature, so there's no workaround.

Also, HTTPS URL is displayed twice in the menu. The first instance looks good, but the second instance has an additional path component with the bucket name, e.g. https://mybucket.s3.amazonaws.com/mybucket/… thus pointing to an invalid path.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you double check you do not have the bucket name included in Server in the bookmark configuration. It should be set to s3.amazonaws.com.

@cyberduck
Copy link
Collaborator Author

08762be commented

True. That fixed it, thank you!

I was misled by how the AWS console generates URLs with the bucket name included as a subdomain.

@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.
Assignees
No one assigned
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck