Skip to content

Interoperability with Eucalyptus S3 #8216

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.

Sign up for GitHub

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
Closed
cyberduck opened this issue Sep 10, 2014 · 3 comments
Closed

Interoperability with Eucalyptus S3 #8216

cyberduck opened this issue Sep 10, 2014 · 3 comments
Assignees
@dkocher
Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Milestone
4.6

Comments

@cyberduck
Copy link
Collaborator

7bf3901 created the issue

After upgrading from version 4.5 to 4.5.2 the ability to browse S3 buckets in a Eucalyptus 4.0.1 cloud breaks. Cyberduck starts trying to navigate to . when it needs to go to these buckets via the URI rather than the hostname.

For example

  • https://objectstorage.euca.ifmsystems.com:8773/services/objectstorage/ifm-dataportal-dev/apps/apb-chrysler/
    not https://ifm-datapotal-dev.objectstorage.euca.ifmsystems.com/...

I used the following profile on both versions
@cyberduck
Copy link
Collaborator Author

@dkocher commented

This issue was introduced with c65f104.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed default context path in profile in 7d97b6e.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 0814e95.

@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.
Assignees

@dkocher dkocher

Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.6
Development

No branches or pull requests
2 participants
@dkocher @cyberduck